Home > Archive > Clipper > June 2006 > Clipper 5.2 app slows down my network
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Clipper 5.2 app slows down my network
|
|
|
| Hi folks,
We have a network which has a WinNT 4.0 server box, a bunch of Win2K
workstations and a Win98 SE workstation.
The Clipper app is located on the NT box, with all the data it needs. The
app is always started from the Win98 box and when it does, it significantly
slows down the whole network. The app does not continuously work with the
DBFs. It justs opens them (about 4) and doesn't do much with them. The
indexes are NTX.
If the Clipper app isn't running, then all works fine.
Any ideas ?
Steph
| |
| E. Fridman 2006-06-05, 6:55 pm |
| Does any Clipper code run on a Server?
Does the app have CPU time release functionality?
========================================
=======
Steph wrote:
> Hi folks,
>
> We have a network which has a WinNT 4.0 server box, a bunch of Win2K
> workstations and a Win98 SE workstation.
>
> The Clipper app is located on the NT box, with all the data it needs. The
> app is always started from the Win98 box and when it does, it significantly
> slows down the whole network. The app does not continuously work with the
> DBFs. It justs opens them (about 4) and doesn't do much with them. The
> indexes are NTX.
>
> If the Clipper app isn't running, then all works fine.
>
> Any ideas ?
>
> Steph
| |
| Nick Ramsay 2006-06-06, 3:55 am |
| On Mon, 5 Jun 2006 11:14:00 -0400, "Steph" <sgtpepper@bootcamp.com>
wrote:
>Hi folks,
>
>We have a network which has a WinNT 4.0 server box, a bunch of Win2K
>workstations and a Win98 SE workstation.
>
>The Clipper app is located on the NT box, with all the data it needs. The
>app is always started from the Win98 box and when it does, it significantly
>slows down the whole network. The app does not continuously work with the
>DBFs. It justs opens them (about 4) and doesn't do much with them. The
>indexes are NTX.
>
>If the Clipper app isn't running, then all works fine.
>
Dodgy network card generating a broadcast storm?
| |
|
| Guys,
I'll reply to all here:
E. Fridman:
No clipper code runs on the server
What's CPU time release functionality ?
Nick:
Everything behaves when the app isn't running on that PC.
If the card was faulty, wouldn't it affect the network even if the app
wasn't running ?
Dave:
Tcp/ip on a WinNT server 4.0 Domain
Thanks,
Steph
"Steph" <sgtpepper@bootcamp.com> wrote in message
news:ZSXgg.462$LV.29330@news20.bellglobal.com...
> Hi folks,
>
> We have a network which has a WinNT 4.0 server box, a bunch of Win2K
> workstations and a Win98 SE workstation.
>
> The Clipper app is located on the NT box, with all the data it needs. The
> app is always started from the Win98 box and when it does, it
significantly
> slows down the whole network. The app does not continuously work with the
> DBFs. It justs opens them (about 4) and doesn't do much with them. The
> indexes are NTX.
>
> If the Clipper app isn't running, then all works fine.
>
> Any ideas ?
>
> Steph
>
>
| |
|
| is the win98 machine networking peer to peer
or ipx , tcpip through the netware server
"Steph" <sgtpepper@bootcamp.com> wrote in message
news:ZSXgg.462$LV.29330@news20.bellglobal.com...
> Hi folks,
>
> We have a network which has a WinNT 4.0 server box, a bunch of Win2K
> workstations and a Win98 SE workstation.
>
> The Clipper app is located on the NT box, with all the data it needs. The
> app is always started from the Win98 box and when it does, it
> significantly
> slows down the whole network. The app does not continuously work with the
> DBFs. It justs opens them (about 4) and doesn't do much with them. The
> indexes are NTX.
>
> If the Clipper app isn't running, then all works fine.
>
> Any ideas ?
>
> Steph
>
>
| |
| Klas Engwall 2006-06-17, 7:55 am |
| Steph,
>What's CPU time release functionality ?
The Clipper runtime is constantly polling the keyboard. When the
application is sitting idle at a read, menu to, inkey(0) etc it uses
almost 100% of the CPU's capacity. There are several different
solutions that will release a few time slices now and then so other
applications running on the same computer also get their share of the
CPU. One of those solutions can be found in the Nanforum Toolkit. Info
and downloads are available at the URL in my sig. You can expect the
CPU usage to drop to 1-2% after implementing it.
A second reason to apply one of the time slice release solutions is
that it prevents the CPU from running hotter than necessary, which
might have an impact on its life expectancy.
But of course, the CPU hogging should only affect the local machine,
not the whole network.
>Everything behaves when the app isn't running on that PC.
And all is well when the app runs on any of the other PCs ???
Have you tried running a network monitor, such as Ethereal for
example, to see if there is a significant increase in network traffic?
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
| |
|
| Klas,
"Klas Engwall" <klas.engwall@nospam.please> wrote in message
news:4487777b.230707539@nntpserver.swip.net...
> Steph,
>
>
> The Clipper runtime is constantly polling the keyboard. When the
> application is sitting idle at a read, menu to, inkey(0) etc it uses
> almost 100% of the CPU's capacity. There are several different
> solutions that will release a few time slices now and then so other
> applications running on the same computer also get their share of the
> CPU. One of those solutions can be found in the Nanforum Toolkit. Info
> and downloads are available at the URL in my sig. You can expect the
> CPU usage to drop to 1-2% after implementing it.
>
> A second reason to apply one of the time slice release solutions is
> that it prevents the CPU from running hotter than necessary, which
> might have an impact on its life expectancy.
>
> But of course, the CPU hogging should only affect the local machine,
> not the whole network.
>
>
> And all is well when the app runs on any of the other PCs ???
It's no use since it won't practically run on Win2K and WinXP. It requires a
special hardware setup anyways. But that setup has no relation to network
hardware.
> Have you tried running a network monitor, such as Ethereal for
> example, to see if there is a significant increase in network traffic?
Nope. Could give some insight.
Thanks,
Steph
| |
| Tom Walden 2006-06-17, 7:55 am |
| Sounds like you need to upgrade to the Advantage Database Engine. Your
network traffic will go down to almost nothing, except for filters. Also
think about switching to CDX's if possible...
Tom
| |
|
| Tom,
This app will be rewritten with VO at some point and it's the only Clipper
app running on the network. I have no intention of modifying it in anyway.
Thanks anyways,
Steph
"Tom Walden" <twalden1NO@SPAMcfl.rr.com> wrote in message
news:CVWhg.7129$7G2.5385@tornado.tampabay.rr.com...
> Sounds like you need to upgrade to the Advantage Database Engine. Your
> network traffic will go down to almost nothing, except for filters. Also
> think about switching to CDX's if possible...
>
> Tom
>
>
| |
| E. Fridman 2006-06-17, 7:55 am |
| Steph,
<<< The app does not continuously work with the DBFs. It justs opens
them (about 4) and doesn't do much with them. >>>
So it loops and waits for something? Does it constantly reads
something from the server while waiting? Checks a content of a
particular directory, polls server time, etc?
Network traffic does not have to be DBF related.
| |
| Klas Engwall 2006-06-17, 7:55 am |
| Steph,
>
>Nope. Could give some insight.
Just run anything that monitors the network and tells you whether
traffic increases or not when the application is started. Ethereal is
just one example (it is a free download, search the web for it). When
nobody runs any application that communicates over the network it just
shows sporadic maintenance messages being transmitted. If your
application is guilty of sending zillions of messages they should show
up in Ethereal (or whatever monitor you use) if it is configured
correctly. When you know what is happening it will be easier to find a
solution.
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
| |
|
| Nick,
"Nick Ramsay" <news@nospam.demon.co.uk> wrote in message
news:e3pg82h6ncte76cpdomtmam8vgn09j0qm9@
4ax.com...
> On Thu, 8 Jun 2006 08:02:46 -0400, "Steph" <sgtpepper@bootcamp.com>
> wrote:
>
>
requires a[color=darkred]
network[color=darkred]
>
> One has to question why the app is on the network at all if it's only
> capable of being run on one machine.
You answered that yourself below <g>
> If it's there because the data is being shared by other programs, it
> sounds much more like the infamous oplock problem than anything else.
Forgot all about that one ! I'll give it a shot.
Thanks,
Steph
| |
| Nick Ramsay 2006-06-17, 7:55 am |
| On Thu, 8 Jun 2006 08:02:46 -0400, "Steph" <sgtpepper@bootcamp.com>
wrote:
>Klas,
>
>
>"Klas Engwall" <klas.engwall@nospam.please> wrote in message
>news:4487777b.230707539@nntpserver.swip.net...
[color=darkred]
>It's no use since it won't practically run on Win2K and WinXP. It requires a
>special hardware setup anyways. But that setup has no relation to network
>hardware.
>
One has to question why the app is on the network at all if it's only
capable of being run on one machine.
If it's there because the data is being shared by other programs, it
sounds much more like the infamous oplock problem than anything else.
|
|
|
|
|