CODEWITHSUNDEEP
performance
Freewind
Freewind

Reputation: 198318

Is 100ms a long time for a simple page rendering?

I'm writing a website, and in my tests, I found each page need at least 100ms to render(total rendering time). The page is simple, and only a few queries to mongodb (There are only several records in mongodb). Is 100ms too long? What's the normal time?

UPDATE

The time is calculated in the server-side, from getting the request, to response.flush. And only one user and one thread to request it. I just found the problem should be in mongodb, it cost nearly 80ms of 100ms.

Back to the question: How long do you think is a good enough time for a normal webpage?

Upvotes: 3

Views: 1862

Answers (2)

Elad
Elad

Reputation: 3130

From a user experience pov (which you should measure on the browser, not server side), under one second feels pretty good, so in principle your 100ms server-side load time sounds great. Actual user experience is affected by many other factors though - latency, javascript, css - take a look at YSlow and its docs for more info.

The real question you should deal with on the server side is what load you're expecting and consequently how the page load time is affected by additional concurrent requests. For instance, maybe with 10 concurrent users it'll take your server 1100 milliseconds on average, not 100, to render a page. You'll need to do performance testing to figure that out.

The advantage of MongoDB and other NoSQL data stores is that they let you scale out (by adding more of the same hardware, rather than scale up - by switching to every stronger and more expensive hardware). In principle MongoDB could scale nearly linearly ad infinitum, meaning that you could (in principle) stay at 100ms load time no matter how many users you grow to - as long as you add more servers.

Upvotes: 1

phpabuse
phpabuse

Reputation: 193

Short answer.

No, in my opinion. 100ms is a short enough rendering time to not annoy users.

Upvotes: 1

Related Questions