|
|
|
|
|
|
by hamandcheese
1398 days ago
|
|
|
I’ve seen instances where the issue is not database performance, but web server performance. Serializing a graphql response in graphql-ruby, for example, can easily take 100+ms and grows linearly with number of records in a request. In the general case this isn’t a good excuse, there’s no reason it should take that long. But you don’t always get to pick your technology. |
|
|