Hi David et. al.,
On the sybase website you guys provide the following graphic in
your jConnect whitepaper.
the whitepaper's explanation of the conditions under which these benchmarks were rendered was woefully incomplete. Would you guys be willing to identify the jConnect competitive product that produced these results? Also could you enumerate the *exact* platform(s) layouts (ie where/on what was the Web server, SQL server, middle-tier server, etc. running?) Was it simply a two-tier JDBC performance competiton? When Jaguar becomes integrated as jConnect's middle-tier solution are you guys planning on running detailed performance benchmarks against other competitive, true, 3-tier JDBC solution providers (ie WebLogic and its T3 product suite?) With true three-tier solutions, notions of JDBC connection pools, persistent client workspaces, middle-tier caching configurations, etc, take on significant importance when comparing and contrasting performance metrics. There are also numerous platform, process, and network performance/load parameters that also must be enumerated in the presentation of results. Hopefully you guys will publish an additional whitepaper that undertakes this burden and delivers a truly informative comparative analysis, possibly even distinguishing jConnect/Jaguar as the clear solution choice.