StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>[C++ programmer]:</p> <p>Ultra-low-latency programming is hard. Much harder than people suspect when they first start down the path. There are some techniques and "tricks" you can employ. Like IO Completion ports, multi core utilization, highly optimized synchronization techniques, shared memory. The list goes on forever. (edit) It's not as simple as "code-profile-refactor-repeat" because you can write excellent code that is robust and fast, but will never be truly ultra-low latency code.</p> <p>Unfortunately there is no one single resource I know of that will show you how it's done. Programmers specializing in (and good at) ultra low-latency code are among the best in the business and the most experienced. And with good reason. Because if there is a silver bullet solution to becoming a good low-latency programmer, it is simply this: you have to know <strong>a lot about everything</strong>. And that knowledge is not easy to come by. It takes years (decades?) of experience and constant study.</p> <p>As far as the study itself is concerned, here's a few books I found useful or especially insightful for one reason or another:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/library/" rel="noreferrer">MSDN Libraries</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0321751043" rel="noreferrer">Art Of Computer Programming</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0201914654" rel="noreferrer">Hacker's Delight</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0131411551" rel="noreferrer">Unix Network Programming: Vol 1</a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/1558605967" rel="noreferrer">Computer Architechture</a></li> <li>Tech journals on the <a href="http://www.acm.org/" rel="noreferrer">ACM</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload