Vodzurk
July 26th, 2004, 04:49 AM
Hi all,
Just wondering if anybody's got a work-around for this problem...
I've made a Client-Server application (not p2p)... and its all working Hunky Dory... until I send a file larger than a meg. Then i get the server CPU locked up for 20 seconds, shortly followed by the client for 20.
This CPU eating grows with the filesize (bit of a problem cos i wanna use 100mb+ files over the LAN).
It seems to happen when encoding/decoding the file into DirectPlay, behind the scenes where i can't get at it (and wouldn't know how to throttle it anyhows).
Anybody have an idea about how to throttle the CPU in this situation?
I was thinking about splitting the files up into 100k packets, and running it in a seperate thread, but this will probably have the same effect for all I know.
Just wondering if anybody's got a work-around for this problem...
I've made a Client-Server application (not p2p)... and its all working Hunky Dory... until I send a file larger than a meg. Then i get the server CPU locked up for 20 seconds, shortly followed by the client for 20.
This CPU eating grows with the filesize (bit of a problem cos i wanna use 100mb+ files over the LAN).
It seems to happen when encoding/decoding the file into DirectPlay, behind the scenes where i can't get at it (and wouldn't know how to throttle it anyhows).
Anybody have an idea about how to throttle the CPU in this situation?
I was thinking about splitting the files up into 100k packets, and running it in a seperate thread, but this will probably have the same effect for all I know.