How not to structure database-backed web apps: performance bugs in the wild

Re:How not to structure database-backed web apps: performanc... by mnm1 on Thursday June 28, 2018 @11:33AM (#17417722)

So the ORM taking many seconds for query overhead isn't a problem? This makes the web page served by this api many seconds slower. A second of slowness increases bounce rate by quite a bit and by two to three seconds, most visitors abandon the website. I guess that doesn't matter to you as you post a comment without substance and only an insult.

[ Parent | on HN ]

Re:How not to structure database-backed web apps: performanc... by falsedan on Thursday June 28, 2018 @11:45AM (#17417852)

I think you have bigger fish to fry than site performance if you're getting 1 hit per day.

[ Parent | on HN ]

Re:How not to structure database-backed web apps: performanc... by mnm1 on Thursday June 28, 2018 @12:30PM (#17418314)

I think you completely missed the point here. If this happens for one customer, it happens for all of them and no amount of hardware thrown at the problem is going to solve this because it's already running on the best hardware available.

[ Parent | on HN ]

Re:How not to structure database-backed web apps: performanc... by olavk on Thursday June 28, 2018 @01:28PM (#17418850)

What ORM setup gives you "many seconds" overhead on a small website? Are you sure the ORM is to blame? I suspect you are doing something like lazy loading in a loop or joining/filtering on the client side.

[ Parent | on HN ]