3 ms·
Could you do a mix of NIC oriented siloing and Disk oriented siloing? It seems like the bottlenecks are different, so if you serve X% of traffic on the NIC nod
by toast0 4y ago
Could you do a mix of NIC oriented siloing and Disk oriented siloing?
It seems like the bottlenecks are different, so if you serve X% of traffic on the NIC node and Y% on the disk node, you might be able to squeeze a bit more traffic?
Also, how amenable to real time analysis is this? Could you look at the request where the request comes in on node A and the disk is on node B, and tell which NIC is less loaded and send the output through that NIC. (Some selection algorithm based on relative loading anyway)
- drewg123 4y agoThose are good ideas. The solution I was thinking of would be to do replication of the most popular content to both nodes.
- toast0 4y agoReplicating popular content is good if there's a smallish core set of popular content. Then you'd be able to serve popular content on the NIC it comes in on without cross NUMA traffic. Really depends on traffic distribution though, if you need to replicate a lot of content, then maybe you push too much content out of cache. It'd be neat if you could teach the page cache to do replication for you... Then you might use SF_NOCACHE for not very popular content, no option medium content, and SF_NUMACACHE (or whatever) for content you wanted cached on the local NUMA node. I'm sure there's lots of dragons in there though ;)