Re: max osc networking
I don't use Max. But I understand that the purpose of OSC is to send messages between different applications, so for me that means communicating between multiple instances of Pd in order to take advantage of multi-core processors.
My gut level feeling is that if you are within one application you should use send/receive as that is it's intended purpose. You are experiencing latency because that's a helluvalot of messages to send at once! Perhaps there's an object that can delay messages so that they are not all piled into one cycle of the message processing rate (look up control rate or message rate and see what advice there is out there) Or this can be solved by using a faster computer (duh, read: rack mount desktop). I built a computer to take advantage of the Linux realtime kernels and haven't looked back but I understand that this would mean a year's worth of work for you transferring to Pd, LOL. Is Max available for Linux, I don't know...?
My GF's dad is one of those old school "knows everything about computers from the ground up" sorta cats and is an engineer at EMC, no less. I asked him about SSDs recently and he warned me that they are not the end-all-be-all. The transistors that store information wear out after 9,000 or so read/writes (forgot which is their weakness, write makes more sense!) He suggested that their appropriate usage is to boot your OS (duh), to boot applications, but not to store data and ESPECIALLY not to be used as swap space (AKA virtual memory).