pyodbc is consuming 90% of my api call time. How to optimise it?

[AjayEdupuganti]

My api call time is 6seconds and this pyodbc consuming 5.5 seconds. Out of which majorly is being consumed by fetchall in cursor.
How can i optimise this?

[v-chojas]

It's unlikely to be pyODBC itself, and probably waiting for the DB server. If only you'd provide more information about your environment, maybe then we might have a better idea what's going on...

[gordthompson]

you are saying 450ms to fetch 10k records is the python's best?

No, that's just the result I got while testing on my database over the LAN in my office. Other environments will produce different results.

But is there a way to optimise it? Or is this how it is?

As far as .fetchall() itself is concerned, that's just how it is.

[AJAYKE]

so you are saying vertical scaling will improve the performance of the db calls.

[v-chojas]

In any case unless you can show the bottleneck happening in pyODBC code and not elsewhere, this is not the fault of pyODBC.

[AJAYKE]

@v-chojas so you are saying, the bottleneck could be because of poor network connection and might not be cursor.fetchall()

[v-chojas]

That's for you to figure out.