Twitter | Search | |
Joe Stump
On a primed cache, your experience should be 100x faster now. On an unprimed cache a mere 10-15x faster.
Reply Retweet Favorite More
Justin Jackson 28 Nov 12
definitely faster load times for Dasboard, individual cards, and items. Activity stream still takes a little while.
Reply Retweet Favorite
Joe Stump 28 Nov 12
Yeah, only a mere 3-5x improvement there. That's actually entirely frontend slowdown now (too much JSON). More to come!
Reply Retweet Favorite
Josh 28 Nov 12
is that all? :P
Reply Retweet Favorite
Joe Stump 28 Nov 12
We've got a clear path to do another 100x over what we have now. ;)
Reply Retweet Favorite
JP 28 Nov 12
What the secret sauce? :)
Reply Retweet Favorite
Joe Stump 28 Nov 12
Going back and profiling/optimizing after melting your face off launching 1.0. ;)
Reply Retweet Favorite
Shawn Smith 28 Nov 12
prime me up then!
Reply Retweet Favorite
Joe Stump 28 Nov 12
Just load your dashboard and then refresh. ;)
Reply Retweet Favorite
Ken Rudman 28 Nov 12
Bring it! We've got work to do.
Reply Retweet Favorite
Jared Mooring 28 Nov 12
would love to see a tech article on your caching solutions.
Reply Retweet Favorite
Marshall ™ 28 Nov 12
did you *just* add cache now!? :)
Reply Retweet Favorite
Justin Abrahms 28 Nov 12
We've had caching for a while. We just cleaned up the number of db queries. ORMs abstract it soo much! /cc
Reply Retweet Favorite
Chris Streeter 21 Jan 13
are you guys using Django for ? If so did you build your own cache library or use one out there?
Reply Retweet Favorite
Joe Stump 21 Jan 13
We use the standard Django cache library. Have avoided ORM-based ones as they were all super buggy/simplistic.
Reply Retweet Favorite
Chris Streeter 21 Jan 13
gotcha. Are you handling invalidation in signals then?
Reply Retweet Favorite
Joe Stump 21 Jan 13
Yeah. That works well near as I can tell.
Reply Retweet Favorite