>Imagine replacing poor in-memory reimplementation of database queries that most graphql servers do with actual opttimised database queries. And a better code o

>Imagine replacing poor in-memory reimplementation of database queries that most graphql servers do with actual opttimised database queries. And a better code on top. but you are actually talking about optimizing system design, and not reducing virtual functions calls :). And that the point of this thread: you need to optimize parts that slow you the most. So no, in most cases optimizing virtual calls won't bring you from 1s to 30ms