Vidar,
The performance depends on a few things:
- how complicated the lens templates are - see if you can simplify them,
use CSS classes instead of style attributes.
- how many facets there are, and how many choices are in each facet -
avoid using facets whose choices have counts of only 1.
- how many items are shown - add ex:showAll="false" to your tile and
thumbnail views so that only 10 items are rendered at first.
- of course, the machine on which you're viewing the exhibit.
And when you said performance, did you mean the load time or the
interactivity?
Exhibit 2.0 (warning: not released yet) has been sped up a little bit,
might be noticeable if you have lots of facets. I personally haven't had
much problem with the map view being slow. How's this exhibit working
for you on your machine?
http://ryanlee.org/2007/04/conflicts.html
David
Vidar Falkenberg wrote:
> I am building an exhibit with data from a Google spreadsheet. As the
> amount of data and facets grows, it seems that performance is heading
> towards unacceptable. Would there be a difference if I used JSON to store
> the data? There are currently approx. 200 items with 25 properties, and I
> think it will grow to maybe 300 items. The biggest problem is when I use
> the map view, but that has perhaps nothing to do with spreadsheet vs. JSON?
>
> I also have some (or rather, a lot!) of other questions, but they'll have
> to wait to my exhibit is ready to be, well, exhibited. I consider
> switching to Exhibit 2.0 - are there any difference in performance between
> 1.0 and 2.0?
>
> /Vidar
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
>
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
