Hi Subodh,
10k records isn't that much. Nonetheless you should test your
application with high loads to assert if the database performance is an
issue.
If the test results show that the database performance may be a problem,
you should check if the tables you use are properly indexed and look for
a caching mechanism.
Configuring cache in Django is fairly easy. I use Memcached as cache
backend with Django. I have a database of about 6 Million users (mysql),
and on each of the 3 frontends running Django, I have an instance of
memcache running.
Rui Silva
On 03/04/2013 11:08 PM, Subodh Nijsure wrote:
Hi,
I have implemented a django application that willl maintain schedule
for 100s of people that work for a company. People access this
schedule using desktop or mobile device to lookup their task list for
current day, this week etc.
Now the question is how do I scale this -- example when user joe looks
up his schedule for today essentially I end up doing a query get
records for today, where user name is joe. Same thing would happen
when Mary looks up her schedule, we do DB lookup for records for Mary.
I am worried that when 10,000 people start to query this my database
is going to become a bottleneck (?) Should I be implementing some of
home grown daemon that caches the data associated with most common
queries and serve the data out of that daemon.
I am sure I am not the first one to encounter this issue, how do
people scale their query response time when using django as their
framework.
(Hope this Q made sense...)
-Subodh
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
