The cursor library is the last place I would expect a bottleneck. Since you say it's quick on your newer stack, I would first suspect a network issue ... either something solvable like a DNS resolution timeout or something semi-insolvable, like the client forcing everything through a slow VPN. Some timing numbers -- either via Benchmark or DBI_TRACE should help you pinpoint the issues.