> -----Oorspronkelijk bericht----- > Van: [email protected] > [mailto:[email protected]] Namens > [email protected] > Verzonden: Thursday, December 17, 2009 20:07 ... > Given the raw performance of C over C#, this means that an > IOCP implementation of ENet would probably scale to 10x as > many packets per second before dropping packets.
It depends on what you do; for internet games (one of the targets of ENet it seems), any bandwidth that you could transfer over the internet gives a negligible impact on CPU. There's just not that much you can and want to transfer. So I think the impact of IOCP there would be zero. Besides, most internet flow just flows to a single thread, handling network (and probably other things). For video transfer on LANs for example, things like IOCP might be nice. Even then, probably ENet would follow a cross-platform multithreaded approach rather than using proprietary API's, but that may just be my cross-platform mindset. ;-) Any non-LAN (internet) app would have nothing to gain with IOCP, is my humble opinion. Cheers, Ruud _______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
