Performance problems

Post #94,295

4/4/03 8:25:53 AM

A client of mine is running Netware, current version on HP server, 700mhz. When he runs a Paradox query it takes him about 30-40 seconds to get the result table. Doesn't matter what the network load is, happens when he is the only user or when the system is loaded (10-15 users).

I have his entire database on my network at home. RH7.1 on a Compaq 5000 (4x200mhz PPro) server (over kill, but it was cheeeeep). The same query produces a result table is 3-5 seconds.

I think his server has more RAM than mine.

Both have 100mb ethernet. Queries are structured the same, tables are structured the same, workstations are comparable (his is slightly new/better than mine). Other than the server/NOS I don't see any difference.

Short of bringing my server down to his office, any troubleshooting suggestions?

[link|mailto:jbrabeck@attbi.com|Joe]

Post #94,300

by boxley

4/4/03 9:11:50 AM

check his network for a troubled hub etc

can he run his query elsewhere on the net and get a different result. Check latency on various boxes in his shop.
thanx,
bill

will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]

questions, help? [link|mailto:pappas@catholic.org|email pappas at catholic.org]

Since corporations are the equivelent of human but they have no "concience" they are by definition sociopaths

Post #94,313

by jbrabeck

4/4/03 9:46:10 AM

Hub

The server is located in his office. His connection is physically next port on hub from server. We could check port by moving both his connection and then server connection to different ports on the hub.

Or, I could bring a different hub for testing.

[link|mailto:jbrabeck@attbi.com|Joe]

Post #94,322

by folkert

4/4/03 10:00:04 AM

Opportunistic Locking... and Buffering/cache

Turn off Oportunistic locking and increase the cache in the Netware Client Settings.

OH, iffn you are not using the Novell Client for Netware... Download it and install it. You can be MUCH more analy retentive about how the client works that way and can usually nail it down.

BTW, before all this... Make sure the Client is running the same frame-type as the server... if the server has 802.2 and 802.3 bound to the interface... well ick.

I use exclusively Ether_II now. Then there is just one frame type the "hub/switch" has to deal with.

b4k4^2

[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT

[link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!]

[link|http://www.eweek.com/article2/0,3959,857673,00.asp|Microsoft develops apps for Linux by 2004]

Heimatland Geheime Staatspolizei reminds:
These [link|http://www.whitehouse.gov/pcipb/cyberspace_strategy.pdf|Civilian General Orders], please memorize them.
"Questions" will be asked at checkpoints.

Post #94,695

by Brandioch

4/6/03 5:58:14 PM

Cross-over cable and connect straight to server.

This will kick everyone else off the network, but it will check whether there is a hardware problem on the network.

Also check server utilization on the monitor screen. What happens when he's running it?

The database is NOT compressed, correct? I don't believe that ANY NetWare server should have compression enable on ANY volume. Compression degrades responsiveness.

Welcome to IWETHEY!