Thank you. It's the age old problem between management and development. I'd say develop on a small server, and then test how far it can go. But someone wants to know _now_.
Am Montag, 27. Juli 2015 19:04:26 UTC+2 schrieb alvaro.rosa1985: > > Não entendi nada. > > Erik Cederstrand <[email protected] <javascript:>> escreveu: > > > > >> Den 27/07/2015 kl. 07.32 skrev Ingo Hohmann <[email protected] > <javascript:>>: > >> > >> Hi, > >> > >> I'm new to django, and I would like to get a hint about system > requirements. If you know about any helpful links, these are welcome, too. > So far what I dog up by googlng wasn't too helpful. > >> > >> Currently we have a > >> > >> - Database with mostly static entries in the thousands > >> - it should be possible to search the database on different fields / > over several fields > >> - the data contains images, as well > >> > >> And the spec says: Expect unexpected changes in several ways. > >> > >> I guess things like voting and commenting will come. > >> > >> Maybe later some sort of api access ... > >> > >> Do you have a rough idea, what kind of setup will be needed? > > > >There is absolutely no sensible way to answer this question in terms of > hardware. For all we know, you could be describing the specs for > google.com, or the intranet for your county church. Everything depends on > what your service needs to do, how many visitors you have, and how fast > they need a response. > > > >My suggestion would be to start with some cheap or free hosting and hack > away. While writing your software, you should always keep in mind the load > you expect/dream for, and make sure you are prepared to add whatever > solutions are necessary to handle increasing load. Prepare yourself by > collecting performance metrics for your software and your hardware, and > define what response times your visitors should expect. > > > >Do performance tests before launch with whatever artificial traffic you > can generate. Hardware requirements are roughly proportional to the number > of requests. Know where your hot spots are and what you can do to solve > them. As real-world traffic starts coming in, look at your metrics. To > increase performance, you can either improve your software or add hardware. > The former is expensive in salary, the latter is expensive in invoices. > > > > > >Erik > > > >-- > >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] <javascript:>. > >To post to this group, send email to [email protected] > <javascript:>. > >Visit this group at http://groups.google.com/group/django-users. > >To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/F69A1D5E-35EE-427C-9EA2-E6FB0A277523%40cederstrand.dk > . > >For more options, visit https://groups.google.com/d/optout. > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d77ff4d1-f103-428b-8572-5c95b4558f9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
