There is no way you can give an answer based on an application that doesn't exist, and a server that doesn't exist. What I would do is give them real numbers based on an application you -can- test. Build a tiny Django application that does something resonably representitive of what the real application average page would be, and use one of the testing tools to generate your own data. Maybe a simple virtualbox/ vmware image you can archive. Document the test, configuration, equipment, and code for a footnote reference. If you give them real data, and fully disclose how you got it gives them what they want and covers your ass.
Something like this: http://scottbarnham.com/blog/2008/04/28/django-performance-testing-a-real-world-example/ On May 6, 9:52 am, Roberto Cea <rodrigo...@gmail.com> wrote: > I am in the process of signing a contract to develop a website for a > fairly large IT company using Django. They requested that the contract > nclude: > > 1) number of concurrent visitors that the site will support > 2) maximum response times for typical requests > > I've explained that both items will depend finally on the server > hardware, which they will provide, but they still want some ballpark > figures. > I realize that a precise answer would depend on the specifics of how > the site is programmed, but wonder if anybody has any idea or > experience answering this kind of question? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
