Earlier quoted context omitted.
It does not consume much memory but do lots of allocations/deallocations. No disc operations whatsoever.
M1 has a larger L1 cache, but smaller L3 cache. It could very well be that your application is hitting a memory pattern that favors larger L1 cache, while the huge L3 cache of EPYC is not useful. ------ If you really wanted to know, you should learn how to use hardware performance counters and check out the instructions-per-clock. If you're around 1 or 2 instructions per clock tick, then you're CPU-bound. If you're l…
Ask HN: Running production server on M1 mini?
61–65 of 65 posts
Re: Ask HN: Running production server on M1 mini?
#62You've got to put some sort of firewall or something in front, don't let it accept tcp connections directly. You might be OK, but not great if you just set the listen queue really short; at least that should prevent the machine from falling over when it's flooded, but without syncookies, chances are you won't be able to make new connections either.
Re: Ask HN: Running production server on M1 mini?
#63Earlier quoted context omitted.
It does not consume much memory but do lots of allocations/deallocations. No disc operations whatsoever.
M1 has a larger L1 cache, but smaller L3 cache. It could very well be that your application is hitting a memory pattern that favors larger L1 cache, while the huge L3 cache of EPYC is not useful. ------ If you really wanted to know, you should learn how to use hardware performance counters and check out the instructions-per-clock. If you're around 1 or 2 instructions per clock tick, then you're CPU-bound. If you're l…
I have dabbled with the AMD & Intel Xeon side of this, but never on MacOS. Do you have an idea how one would go about getting performance counters on MacOS? IPC, L1hit/miss, L2 hitless etc.
Re: Ask HN: Running production server on M1 mini?
#64As per the stability, my scaleway m1 has never had any issues. works just fine for some CI.
Re: Ask HN: Running production server on M1 mini?
#65Earlier quoted context omitted.
M1 has a larger L1 cache, but smaller L3 cache. It could very well be that your application is hitting a memory pattern that favors larger L1 cache, while the huge L3 cache of EPYC is not useful. ------ If you really wanted to know, you should learn how to use hardware performance counters and check out the instructions-per-clock. If you're around 1 or 2 instructions per clock tick, then you're CPU-bound. If you're l…
This. I have dabbled with the AMD & Intel Xeon side of this, but never on MacOS. Do you have an idea how one would go about getting performance counters on MacOS? IPC, L1hit/miss, L2 hitless etc.