Skip to content
Discussion options

You must be logged in to vote

if sequentially execution is bad for app performance or it is normal if just one connection has established

Inside a transaction, that is pretty much the only way. Apps usually read more data than they write, where not transactions are required, and there it makes total sense to send queries in parallel instead of sequentually.

in other way if i loop inside transaction for 100 iteration and each loop make query is that send to db server 100 request and if happend; is that a big case?

If you are sending 100 queries in a loop, that is the problem. Find a way to combine these queries by for example collecting all the data in the loop first, and then sending one query instead.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@Abd-elrahman2003
Comment options

@janpio
Comment options

Answer selected by Abd-elrahman2003
@Abd-elrahman2003
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants