forum.vdsworld.com

webdaddy · Posted: Sat Oct 01, 2005 3:14 am Post subject: VDSIPP Question

I know the DLL is not longer supported but I have a question. I have an application that im playing with that is basically the equivelant to portmon which is provided as a demo in VDSTCP package. I wrote something similar in VDSIPP. Some of the details are as follows. In VDSIPP i am basically listening on 30 ports. When I run my application it uses about 8MB of memory and 0-1%CPU. As soon as I scan the system with a portscanner to test it my memory utilization goes to 12MB (not a big deal) but my CPU spikes to 99/100%.

Is this normal. I mean I use VDSIPP in several applications (servers) and I dont have any issues. Its just when I load up several listening ports that the problem rears its ugly head. Is this just designed to listen on 1 port per application or am I just doing something wrong?

Maybe time to register the VDSTCP stuff and start using it instead?

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1565

If you are listening with the TCP or UDP protocols then yes it will utilize high amounts of cpu. This is due to each instance running an internal timer to check for incoming messages and triggering an event in vds when a message comes in - thus in your case around 30 timers.

webdaddy · Posted: Sat Oct 01, 2005 7:05 pm Post subject: Fix

Is there anyway to fix this? Or is it a limitation of the DLL itself?

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1565

Unlikely because the dll has to catch any incoming events for tcp/udp and then trigger an event in vds. The only way would be to rewrite the entire tcp/udp servers so no event is ever triggered and allows the vds script itself to manually check (with a single time) for the buffer in each tcp/udp server message stack to see if any message recently came in.

webdaddy · Posted: Sat Oct 01, 2005 8:20 pm Post subject: Thanks

Thanks. I will use the other TCP libary for this application. So basically I should only use VDSIPP for single daemon type operations to keep the utilization low and manageable. Not a problem. Thanks for your quick responses.

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1565

The TCP/UDP functionality of vdsipp while functional has some major restrictions. The real promise in VDSIPP are the more mainstream protocols - smtp/pop/ftp/http, etc where much of the coding and wrapping of the tcpip layer is handled automatically.