Posted by Jim Guerber on August 02, 2010 at 15:30:59:
In Reply to: Comet Services on 64-bit vs 32-bit platform...> posted by Tom Fulton on August 02, 2010 at 11:28:38:
This is very interesting. Do you still have the test configuration around so we could figure this out?
It could be 64 bit vs 32 bit. But from your writeup, it seems that the bottleneck is in the tcp/ip connectivity of your systems. It is correct that in all cases of slowdown, you were talking from a comet workstation to a comet server on a different IP address, right?
Comet keeps a connection open for a long time vs other apps like http that make an ad hock connection, do a little transaction and then close it. It is analogous to windows copying a long file to or from a server. For your test4 example, Comet performs each action and then waits for a response from the server. This is many turn-arounds in a very short time.
I googled "windows 2008 server tcp slow" and I am seeing several similar problems. Microsoft changed their winsock stack with the release of vista and win2008. Would you be willing to try the suggestions listed below to see if the performance could be improved?
Following is the simplest fix. There are other suggestions as well.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.