RE: Speed test for connecting to Oracle for Windows via ODBC
- From: FowlerM@xxxxxxxxxxxxxxxxx (Mark Fowler)
- Date: Tue, 13 Jun 2006 11:29:17 -0300
Apologies, I was making a general observation. I was more interested in
making the exercise easier for others, as my own situation is probably an
obsolete issue. All those technical aspects necessary to obtain a solution
were provided during 2004, and some would no longer be valid (e.g.
esoftmatic ppd's, versions of Apache, PERL, Oracle, etc). You are quite
right to assume that DBI was not the problem. It was determined that the LAN
configuration was the problem (various degrees of bottlenecking among
network nodes), but without being able to specify the exact details, largely
due to disinterest on the part of LAN support with respect to non-standard
software. My point is that it would have been helpful if I could have
demonstrated without ambiguity what aspects of the configuration were
responsible for the bottlenecking, and what changes would have rectified the
problem. Perhaps this is not considered to have any bearing on DBI, but this
list is where I most often see the question raised.
I received a post from Job Miller pointing me to 'How to Perform Client-Side
Tracing of Programmatic Interfaces on Windows Platforms'. I haven't been
able to obtain this yet, but hopefully this sort of thing makes the task
easier for folks wrestling with DBI connectivity issues. I feel it important
for users within a Microsoft-centric environment to have a better handle on
networking when attempting to use open source communications software. An
'ask support' response may not be helpful in many of these cases.
Mark FowlerPopulation Ecology Division
Bedford Inst of OceanographyB2Y 4A2
Dept Fisheries & Oceans
Dartmouth NS Canada
Tel. (902) 426-3529
Fax (902) 426-9710
Email fowlerm@xxxxxxxxxxxxxxxxx
Home Tel. (902) 461-0708
Home Email mark.fowler@xxxxxxxxxxxxxxx
-----Original Message-----
From: Matthew Ramadanovic [mailto:matthew.ramadanovic@xxxxxxxx]
Sent: June 13, 2006 10:05 AM
To: 'Fowler, Mark'; Martin Hall; ron@xxxxxxxxxxxxx
Cc: List - DBI users
Subject: RE: Speed test for connecting to Oracle for Windows via ODBC
I can understand frustration but your request is too nebulous for those who
do have the skills to help you troubleshoot. I connect to Oracle from many
different Windows installs daily and have never seen the problems you have
described without other identifiable machine configuration issues (as in the
machine couldn't resolve ANYTHING quickly or had additional software that
contributed - like connecting from a vmware host). The problems were never
specifically related to DBI and were resolvable without the use of this list
so you fix the machine to fix your problem.
Your "blame the network guy statements" miss the point that for a lot of us
we ARE the networking guys and have both programming and infrastructure
skills. Not everyone works in environments where there are lines drawn
between that beginning and ending of our responsibilities - some of us even
deal with users :-)
You mention name resolution but don't go into detail. Are you connecting to
the server IP, the FQDN, or are you using the Netbios name? What OS are you
using and what patch level are you at. How many NICs are in the machine and
what is the binding order on those nics?
Saying it is "slow" is about as useful as saying it is "broken". For people
who want to help it is equally frustrating to hear about problems when they
are half described - I'd help if there was more there and I'm sure other
would as well. I think the reason people don't "solve" this problem is
because they can't replicate it with the information provided and move on to
other fire missions.
-M
-----Original Message-----
From: Fowler, Mark [mailto:FowlerM@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 13, 2006 7:03 AM
To: Martin Hall; ron@xxxxxxxxxxxxx
Cc: List - DBI users
Subject: RE: Speed test for connecting to Oracle for Windows via ODBC
I would like to voice some frustration at the advice to ask
'support' for assistance in this situation. It has been a problem for years
now. Too many requests for help dealing with the PERL/ODBC/Windows problem
with slow connections are dead-ended.
I believe a major hurdle is that a very large proportion of the
PERL/ODBC/Windows requests involve attempts to utilize open source software
from within typically non-open source environments. The network support
often won't consider trying to solve the problem on first principles - it is
not their job to address issues involving non-standard software. In other
cases support staff couldn't help even if willing, they just don't know
enough about either networking in general or open source variants in
particular. Hence when a request for help to the DBI list elicits a response
along the lines of 'You'll have to ask your network admin to investigate at
their end', the problem is unlikely to be resolved.
The specific issue of slow connectivity using PERL/ODBC/Windows from
within a non-open source network has been recurring very frequently for
several years now. I ran this gauntlet in 2004, and it was clear then that
it was an old and essentially unresolved problem. We know it can be fixed
with co-operation at the network admin end, but this only matters if they
both wish and know what to do. A great many users (and would-be users) of
DBI would benefit from a comprehensive treatment of the subject. For
instance, what specifically are the environment parameters that are likely
at fault? Are there ways for the client to circumvent any of these? How can
the client prove that the problem is with the network setup, and not their
own implementation of PERL or DBI? In cases where network support might be
co-operative but not sufficiently knowledgable, can they be guided?
Mark FowlerPopulation Ecology Division
Bedford Inst of OceanographyB2Y 4A2
Dept Fisheries & Oceans
Dartmouth NS Canada
Tel. (902) 426-3529
Fax (902) 426-9710
Email fowlerm@xxxxxxxxxxxxxxxxx
Home Tel. (902) 461-0708
Home Email mark.fowler@xxxxxxxxxxxxxxx
-----Original Message-----
From: Martin Hall [mailto:martin.hall@xxxxxxxxxx]
Sent: June 13, 2006 5:55 AM
To: ron@xxxxxxxxxxxxx
Cc: List - DBI users
Subject: Re: Speed test for connecting to Oracle for Windows via ODBC
Ron Savage wrote:
On Mon, 12 Jun 2006 23:04:04 -0700, Jonathan Leffler wrote:just much worse.
Hi Jonathan
Wellllllllllllllll, I know Oracle has been criticized for taking up to
7 secs to connect in a non-Win evironment, so I assume this is the
same,
I have to say that it doesn't sound right to me. I agree that connecting to
Of course, it could indicate the Oracle developers has a (twisted)
sense of humour, and that this is their way of pressuring users to move
to non-Win platforms :-)).
Either way, it's appalling.
Oracle through ODBC can be slower than straight connects because there's
more information being exchanged between the two sides.
But 14 seconds sounds too long. I would have a word with support and see
what they come up with.
Martin
.
- Prev by Date: DBD::ASAny test cores when using multithreaded, 64-bit Perl
- Next by Date: Re: Displaying fetched values in html form
- Previous by thread: RE: Speed test for connecting to Oracle for Windows via ODBC
- Next by thread: RE: Speed test for connecting to Oracle for Windows via ODBC
- Index(es):
Relevant Pages
|
