On 27/01/06,
dername">Ludek Finstrle <luf@pzkag=
is.cz> wrote:
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;">
> > We have a fully switched 100mbps network, and communication betwe=
en
> > clients running vb6 apps via odbc (08.01.02, i.e., the late=
st stable) are
> > taking up from 20 to 40% of the bandwidth - per=
APP!. The server is
> > 8.1.1running on mandrake 10.1.
You forgot specify the =
client OS ;-)
Yeah, windows xp (I think we have one w=
ith no SP, and the rest with SP1). We have some win2000 sp4s but they don't=
run the offending app (rather other ones that don't show the problem).
olid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">But=
the network bandwidth isn't
psqlODBC related. We use libpq for communic=
ation with backend.
I have seen similar problem a few days ago and Magnus Hagander wrot=
e:
| We've seen this a couple of times before with Windows 2000, but=
it's
| always been slow in both psql and pgadmin then ;-) Search the ar=
chives,
| there's something about the QoS driver.
I looked=
and it didn't seem particularly related, seeing as they are XP boxen.
<=
/div>CPU usage for the postgres machine is also very high, getting regularl=
y up to 50% for a single connection. I will try a vacuum full but I am pret=
ty sure that won't make much difference. Maybe it is related to network tra=
ffic?
I will have a look with ethereal and see what I can gather.
Ch=
rs
Antoine
--
This is where I should put some w=
itty comment.
------=_Part_39542_32135710.1138360165770--
Re: network saturation
am 27.01.2006 15:17:25 von Ludek Finstrle
> I looked and it didn't seem particularly related, seeing as they are XP
> boxen.
> CPU usage for the postgres machine is also very high, getting regularly up
> to 50% for a single connection. I will try a vacuum full but I am pretty
> sure that won't make much difference. Maybe it is related to network
> traffic?
> I will have a look with ethereal and see what I can gather.
Agrh I'm stupid. You feel too high HW load. Do you know what exactly
the app makes? Feel free to create mylog output or you can log on
the server side to have better idea what's going on.
Than you can try simulate the situation via psql client. So you
can decide where is the problem.
If you don't understand the mylog output you could send it to me
privately.
It could be interesting to see what settings do you use for psqlodbc.
BTW 08.01.0102 isn't very good. Please try 08.01.0107 development
snapshot from pgfoundry.org. There is fixed a lot of bugs
(Parse Statement, get values, stability, ...).
Then you can try different options like use declare/fetch, Parse Statement,
.... Different tasks need different options turned on.
We're planning to release new psqlodbc official release next week.
The new official release will be based on the 08.01.0107.
Regards,
Luf
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Re: network saturation
am 27.01.2006 15:40:06 von Antoine
------=_Part_41363_5811816.1138372806803
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
>
>
> It could be interesting to see what settings do you use for psqlodbc.
> BTW 08.01.0102 isn't very good. Please try 08.01.0107 development
> snapshot from pgfoundry.org. There is fixed a lot of bugs
> (Parse Statement, get values, stability, ...).
> Then you can try different options like use declare/fetch, Parse
> Statement,
> ... Different tasks need different options turned on.
>
I would love to try it, seeing as declaire/fetch doesn't change anything...
Do I simple replace the dlls in C:\Program Files\psqlODBC\bin?
Cheers
Antoine
--
This is where I should put some witty comment.
------=_Part_41363_5811816.1138372806803
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It could=
be interesting to see what settings do you use for psqlodbc.
BTW 08.01.=
0102
isn't very good. Please try 08.01.0107 development
snapshot from
f=3D"http://pgfoundry.org">pgfoundry.org. There is fixed a lot of bugs<=
br>(Parse Statement, get values, stability, ...).
Then you can try diffe=
rent options like use declare/fetch, Parse Statement,
... Different tasks need different options turned on.
<=
br>I would love to try it, seeing as declaire/fetch doesn't change anything=
....
Do I simple replace the dlls in C:\Program Files\psqlODBC\bin?
Cheers
Antoine
--
This is where I sho=
uld put some witty comment.
------=_Part_41363_5811816.1138372806803--
Re: network saturation
am 27.01.2006 15:57:01 von Ludek Finstrle
Fri, Jan 27, 2006 at 03:40:06PM +0100, Antoine napsal(a):
> > It could be interesting to see what settings do you use for psqlodbc.
> > BTW 08.01.0102 isn't very good. Please try 08.01.0107 development
> > snapshot from pgfoundry.org. There is fixed a lot of bugs
> > (Parse Statement, get values, stability, ...).
> > Then you can try different options like use declare/fetch, Parse
> > Statement,
> > ... Different tasks need different options turned on.
>
> I would love to try it, seeing as declaire/fetch doesn't change anything...
> Do I simple replace the dlls in C:\Program Files\psqlODBC\bin?
Yes. It's enough.
But it's strange that declare/fetch doesn't change anything.
Driver fetch "cache size" (option on Page1 in left bottom corner) rows
from backend after open. "cache size" is 100 by default. So if you have
less rows in selects you could try to play with the cache size parameter.
Regards,
Luf
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: network saturation
am 27.01.2006 16:07:10 von Antoine
------=_Part_117_25662231.1138374430337
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On 27/01/06, Ludek Finstrle wrote:
>
> Fri, Jan 27, 2006 at 03:40:06PM +0100, Antoine napsal(a):
> > > It could be interesting to see what settings do you use for psqlodbc.
> > > BTW 08.01.0102 isn't very good. Please try 08.01.0107 development
> > > snapshot from pgfoundry.org. There is fixed a lot of bugs
> > > (Parse Statement, get values, stability, ...).
> > > Then you can try different options like use declare/fetch, Parse
> > > Statement,
> > > ... Different tasks need different options turned on.
> >
> > I would love to try it, seeing as declaire/fetch doesn't change
> anything...
> > Do I simple replace the dlls in C:\Program Files\psqlODBC\bin?
>
> Yes. It's enough.
>
> But it's strange that declare/fetch doesn't change anything.
> Driver fetch "cache size" (option on Page1 in left bottom corner) rows
> from backend after open. "cache size" is 100 by default. So if you have
> less rows in selects you could try to play with the cache size parameter.
>
I have tested with the dlls changed (107) and WOW - what a difference!
Thanks! We tried with 102 on another system and it didn't work. We aren't
going to search to hard though cos, hey, we have the best solution!
Thanks heaps
Antoine
--
This is where I should put some witty comment.
------=_Part_117_25662231.1138374430337
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On 27/01/06,
dername">Ludek Finstrle <luf@pzkag=
is.cz> wrote:
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;">
Fri, Jan 27, 2006 at 03:40:06PM +0100, Antoine napsal(a):
> > It c=
ould be interesting to see what settings do you use for psqlodbc.
> &=
gt; BTW 08.01.0102 isn't very good. Please try 08.01.0107 development
> > snapshot from .=
There is fixed a lot of bugs
> > (Parse Statement, get values, st=
ability, ...).
> > Then you can try different options like use dec=
lare/fetch, Parse
> > Statement,
> > ... Different tasks need different op=
tions turned on.
>
> I would love to try it, seeing as declaire=
/fetch doesn't change anything...
> Do I simple replace the dlls in C=
:\Program Files\psqlODBC\bin?
Yes. It's enough.
But it's strange that declare/fetch doesn'=
t change anything.
Driver fetch "cache size" (option on Page1 =
in left bottom corner) rows
from backend after open. "cache size&qu=
ot; is 100 by default. So if you have
less rows in selects you could try to play with the cache size paramete=
r.
I have tested with the dlls changed (107) and =
WOW - what a difference! Thanks! We tried with 102 on another system and it=
didn't work. We aren't going to search to hard though cos, hey, we have th=
e best solution!
Thanks heaps
Antoine
--
This is where I=
should put some witty comment.
------=_Part_117_25662231.1138374430337--