hard time , me too thanks <| sep |> These white kids confusing themselves with black people smh <| sep |> I bought four passes to get the free camping pass , but I didn ' t add the camping pass to my cart . Was I supposed to ? It wasn ' t clear . <| sep |> I think it ' s upside down <| sep |> Aaaaaaaand he ' s out on Sunday . <| sep |> tfw I haven ' t got a single shiny yet in SM <| sep |> this is extra sad <| sep |> Things they laugh on . When a girl laughs on something because it looks like a penis , she is instantly judged by me . <| sep |> I can almost certainly guarantee that is not the issue . Unless they are using SQLite or some horribly malformed MySQL , the database is almost never the source of a bottleneck . The real source of the bottleneck is most likely their HTTP server software andor PHP which I think they ' re using itself . These both have hard concurrency limits and they will freak out error 502 , bad gateway or be unable to fill requests error 524 , timeout under high load . For reference , when I switched DickSeek my now defunct alternate inventory viewer over to MySQL and did some loadconcurrency testing , I could get the full inventory information in approximately 150300 msec independent of load and there is additional overhead on my DB that BD would not have . Preparing the data as gzipped json , which DickSeek does and is more efficient than how BD does it takes about 1015 msec . In years past , the bottleneck was probably throughput as each person tried to retrieve 5000 images at once , although with pagination now that would be less significant but still would contribute to the concurrency issue I suggested . The best way to fix this is to switch to a more concurrencyfriendly backend like Node . js or throw more hardware at the problem . Honestly , the most pragmatic way to deal with this might be by switching how Black Friday sales work altogether . Also , plenty of companies still do HTML generation server side . Even Walmart was using pure PHP to serve their site as recently as two years ago . AJAX is still a fragile technology and most sites still maximize performance and reliability by eliminating technical debt in infrastructure , not software .