[Chandler-dev] Pre-loading items as a performance optimization

[Davor Cubranic]

I just started dogfeeding, so my repository is not too big (a few of my 
own events, plus the OSAF office calendar), but to me it seems that 
switching weeks in Chandler is pretty fast and what feels slow is when I 
change the type of the collection (say from calendar to the dashboard and 
back) or when I start entering a new event. The latter can be particularly 
disconcerting, as I start typing and it takes a second for letters to 
start appearing. I know there is a "new event" performance test, but does 
it measure this kind of "user feedback time", or is it about how long does 
the "create event" operation take when called from Python?

Davor