Closed numeroteca closed 11 years ago
We should focus in the slow behavior of the tool. Coding is not that bad right now, but in the display view big threads takes a lot of time (related to #22).
I've replaced the display view with static images generated by the server. I still need to test this on larger threads, and put in some smart caching logic... right now it regenerates the images every time you view the thread. It should instead regenerate the background images when the thread changes, and regenerate the topic coding overlays when new coding is done.
It is faster now, but we could still work on the fact that the thread.results
method appears to be making tons queries... it should be batching them and operating on the results in memory.
I did some refactoring of the thread.results method and now it is much faster (see 62b0a5f52caee2a261377fbfce38bca2bf24c652)
When coding front pages all the images are loaded. This causes slow behavior for long threads. Only the next/previous 5 images should be loaded. Options: