Re:Ruby Concurrency Final Report
by thibaut_barrere on Friday April 17, 2020 @07:58AM
(#22898224)
Maybe you are referring to https://github.com/rails-sqlserver/tiny_tds/issues/117 ? If that's the case, it was fixed seven years ago :-)
[ Parent
| on HN ]
Re:Ruby Concurrency Final Report
by ketamine__ on Friday April 17, 2020 @09:01AM
(#22898584)
I am referring to that project but the issue I'm referring to is an issue with connecting to multiple servers concurrently. If the servers have poor connectivity then you can only connect to one at a time despite using threads.
Re:Ruby Concurrency Final Report
by thibaut_barrere on Friday April 17, 2020 @09:09AM
(#22898635)
Ok! If you ever find the issue back, I'm definitely interested!
Re:Ruby Concurrency Final Report
by ketamine__ on Friday April 17, 2020 @10:47AM
(#22899396)
You can replicate the issue by doing this:
1) Setup 100-500 sql servers. 2) Artificially increase the amount of time needed to finish connect sequence (> 10 seconds). I have no idea how to do this but it's a likely scenario in my use case of servers on cellular connections. 2) Setup X number of threads to make a connection with TinyTds. 3) Those threads should return immediately but with my testing they did not. Only one connection could be in progress at any given time.
Re:Ruby Concurrency Final Report
by thibaut_barrere on Friday April 17, 2020 @11:28AM
(#22899852)
Thanks! I'll keep this handy in case I multiply the number of connections in my cases.