Re: Microsoft JDBC Driver Performance Degradation
From: Stephen Dybing [MSFT] (stephd_at_online.microsoft.com)
Date: 01/05/05
- Next message: Gert E.R. Drapers: "Re: Microsoft JDBC Driver Performance Degradation"
- Previous message: Gert E.R. Drapers: "Re: Microsoft JDBC Driver Performance Degradation"
- In reply to: Brian Luo: "Re: Microsoft JDBC Driver Performance Degradation"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 Jan 2005 14:43:16 -0800
True, but please note that only "managed" customers (i.e. MSDN subscribers
posting using a registered alias) are guaranteed a response and you're not
posting from a registered alias. Even then, this is not the proper newsgroup
for this topic so even if somebody from the MSDN team does respond, which
isn't likely, they'll simply tell you that this is an off-topic post and
needs to be posted to the proper newsgroup even though it's not a managed
newsgroup and you won't get a response to your post. In short, if you
require a response from Microsoft on this topic, I think you're going to
have to open up a case with Product Support. Sorry!
-- Sincerely, Stephen Dybing This posting is provided "AS IS" with no warranties, and confers no rights. Please reply to the newsgroups only, thanks. "Brian Luo" <BrianLuo@discussions.microsoft.com> wrote in message news:134481F8-0146-443F-9D38-1C84E84BFE8D@microsoft.com... > Thanks for the info. Unfortunately, microsoft.public.sqlserver.jdbcdriver > is > not listed as a managed newsgroup. > > "Gert E.R. Drapers" wrote: > >> You better post this in microsoft.public.sqlserver.jdbcdriver >> >> GertD@SQLDev.Net >> >> Please reply only to the newsgroups. >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> You assume all risk for your use. >> Copyright © SQLDev.Net 1991-2004 All rights reserved. >> >> "Brian Luo" <Brian Luo@discussions.microsoft.com> wrote in message >> news:4652D65A-5666-41E3-9245-A572FEF907B8@microsoft.com... >> > We have been using Microsoft SQL Server JDBC Driver 2.2.0040 in our >> > products >> > to connect to SQL Server 2000 Standard Edition SP3 (8.00.760). Our >> > functional testing went fine but we have run into serious performance >> > degradation under simulated heavy loads. >> > >> > Our server crashed with OutOfMemory errors due to the inability to >> > create >> > new native threads for the BaseQueryTimeoutEnforcer class in the JDBC >> > driver >> > library. Right before crashing, we saw high thread counts went from 150 >> > to >> > as >> > high as 490. Thread counts were variable, so the thread count would >> > decrease >> > and increase over time, until the last thread count reported 489 just >> > before >> > crashing. >> > >> > Total GC time was much higher as well due mostly to incremental GC >> > times >> > that were almost 3x that of the benchmarked WebLogic's jDriver. >> > Correspondingly, response times were much higher. >> > >> > I wonder if anyone else has experienced such problems. >> > >> > Thanks, >> > Brian Luo >> >> >>
- Next message: Gert E.R. Drapers: "Re: Microsoft JDBC Driver Performance Degradation"
- Previous message: Gert E.R. Drapers: "Re: Microsoft JDBC Driver Performance Degradation"
- In reply to: Brian Luo: "Re: Microsoft JDBC Driver Performance Degradation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
