> On Aug 12, 2025, at 2:29 PM, Daniel Schwartz <d...@danielgschwartz.com> wrote:
>
> Hello Felix,
>
> See my replies marked with DGS.
>
> Dan
>
> DGS: I explained this in a previous email. Each user interaction requires
> either 3 or 4 database queries. That’s how my system works. There’s no way
> around this. But it’s really quite quick. Three of the four queries are
> simple SQL table look-up queries; only one requires any complex computations.
>
We can’t see exactly how those three queries are performed. They could be:
- on three separate and serial db calls
- all rolled into a single batch of DML
- each sql statement sent simultaneously (nearly) on a separate thread.
The first two require only one db connection. Each call will acquire and
release the connection. And the first of those will hold that connection for
the shorter time, the second for the longer time.
The third option will possibly finish the db work fastest id the is no
contention amongst the queries. But this is the only one which requires more
than one simultaneous db connection.
Does any of these match your architecture?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
