Case 1
| |
| DIOCP is a very good open source framework for the development of IOCP service-side communications under Delphi, which is stable, efficient and easy to use. Myself two months ago because of the need to use Delphi to develop a TCP server, was also crawling around the text, hoping to find a stable and useful IOCP open source framework, a whole week of time, see a lot, also contrasted a lot, finally chose DIOCP, Now the server side of the official version has been online for 36 days, all running stable, whether it is CPU usage, memory use or communication stability, DIOCP performance really did not let me down, performance is very good. Server environment:
os:windows Server 2003
Cpu:intel dual-core Memory: 2G
Net Bandwidth: 5M
Network type: BGP
Actual performance data:
program user simultaneous online: 1200–1300 Peak: 1511 (this peak is real users at the same time online, not theoretical performance peaks, the current number of users only these, the test of their own time, the number of connections tested over 5K, also run stable).
server-side operation to the publication has been more than 36 days, memory peak is only 76m,cpu occupancy has been stable under 10%, should say the indicators are very good, very satisfied. |
QQ:
Tiger |
|
| Case 2< nontoxic Princess > |
| Server-side application scenarios: Financial industry trading quotes, trade control orders released push server. The main is to be stable and fast, the load requirements are not high. Daily Online 20 or so. Both the server and the client use the DIOCP implementation of the IOCP Asynchronous Pattern. Because it is a financial application, the stability and push real-time performance is very high requirements (key time if the instruction delay long, will lose the real money), and all the way along with DIOCP1 to now DIOCP3 stable more than a year, all aspects of performance fully meet the demand. |
|
| Company Name: A financial investment company |
|
| DIOCP version: From DIOCP1 to DIOCP3 < custom encoders > |
|
| QQ Nickname: Princess Wudu (782834) Suggestions and questions: I'm still a very small-scale application, but there are different clients (command control, Administrator, trading terminal) will log into the system, the number of different clients after the agreement will be much more. It is now possible to differentiate the business layer by the command word on a codec. Although it can meet the demand. But it is always felt that the management of the protocol would be cumbersome if a very large and complex system was to be done. So if you can have a server open multiple ports, each port has its own online list, different clients to log on to different ports, the application of different codecs, but also unified management (should be different clients before the need for data intersection, forwarding) this is excellent. |
|
