> The CRSP US Total Market Index, by contrast, adds all IPOs ranging from mega caps to small caps—accounting for 98% of the market—within the first five trading days of the stock’s listing.
So it sounds like SpaceX will show up in VTI sooner than in the Nasdaq100, even with their new "fast entry" rule.
Freakonomics interviewed Dan Wang about his book Breakneck back in September, see episode #647. It's a very interesting lens through which to view both societies, worth a listen!
NPR Planet Money did a segment on pig butchering scams back in May. They played along with one to get a first hand perspective of the process. It’s a fascinating listen, way more complicated than I thought, and tragic for both ends of the scam.
mod_php does give you better response times for individual requests, but at the expense of being able to handle a higher load of traffic; you'll run out of memory and/or experience timeouts on mod_php way before you do with php-fpm.
With mod_php, every Apache process has the PHP engine embedded in it, even if PHP isn't needed, e.g., to serve a request for a .css file. When Apache gets a bunch of requests for flat files, it forks all those processes and fills up RAM with copies of the PHP engine that aren't used. That's not only wasteful, but it dramatically increases the chances that you'll run out of memory. You can limit the number of Apache children of course, but you'll see timeouts sooner when you get a traffic spike.
By having Apache proxy over to php-fpm for PHP requests, you can configure Apache to use mpm_event for serving static files, which allows for much leaner Apache workers (memory-wise) since they aren't carrying PHP around on their backs.
While you're at it, you can use haproxy on the same machine for TLS termination, then you can disable mod_ssl thus making Apache workers even lighter.