3 ms·
I've worked on a widely used NHS IT system and specifically looked at login times for it. We had an issue at one site where instead of taking 30 seconds to log
by cs02rm0 7y ago
I've worked on a widely used NHS IT system and specifically looked at login times for it.
We had an issue at one site where instead of taking 30 seconds to log in it took over 20 minutes. Our JDBC driver was using the default fetch size and the network latency was killing it.
As you may be able to tell, that had nothing to do with authentication - it was a thick client that downloaded a bunch of reference data at login. I left that role well over a decade ago but I've been back into a hospital in the last year or so and it was still in use, in fact, I couldn't see that it had changed at all.
Good luck to them, it's money well spent, but I doubt £40m is going to fix much.
- sumedh 7y ago> JDBC driver was using the default fetch size... it was a thick client that downloaded a bunch of reference data at login not exactly sure what you mean, was the login sql query fetching more data than needed in that case shouldn't you tweak the query?
- cs02rm0 7y agoNo, the data was necessary (though there are a stack of different optimisation strategies they could have pursued with varying trade offs). Fetch size is a standard JDBC parameter for tweaking the number of rows paged in a database query. The Sun/Oracle default was 10 rows and the app needed to retrieve thousands. So it would retrieve 10, process them, retrieve 10 more, etc. Which was minimal overhead on most networks, but on a network with high latency it meant there was perhaps a couple of seconds delay with each fetch.