The CRSP index itself adds new companies within 5 days of their IPO, see https://www.crsp.org/what-owning-the-market-really-means/

> 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.

https://www.npr.org/2025/05/23/1253043749/pig-butchering-sca...

I also recall in the early 2000's hearing people call .html files "hotmail files".

https://toolbox.googleapps.com/apps/dig/#A/faa.gov

I really regret having spent so little time interacting with my professors though. I was one of those kids that spent the least amount of time in class possible, almost never going to office hours, aiming to get the course work out of the way asap so I could "have a life". So much wisdom and life/industry experience was concentrated on that campus and at my fingertips, but I totally took it for granted. Seeing his obit amplifies this feeling; I wish I had cared enough at the time to meet and know the guy.

Will these converge on a common syntax for vector fields, indexes, and comparison functions in the near future? Or will vector implementations just add momentum to the increasing incompatibility in the MySQL-ish ecosystem?

In this initial preview, there is not yet a dedicated VECTOR data type, as they've focused on implementing a usable indexed search.

Comments URL: https://news.ycombinator.com/item?id=41119850

Points: 2

# Comments: 1

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.

Most painful? Replication with automatic failover could be easier to setup. Considering switching to MySQL 8.x for the new-ish innodb cluster tools (mysqlsh, mysql-router).

Why not Postgres? Familiarity, mostly using it for Drupal & Wordpress sites where MySQL is king. Besides the occasional poorly-designed query that eats memory and causes timeouts, MySQL rarely needs my attention.

Side note: I'm excited for https://github.com/mydumper/mydumper. Multi-threaded logical backups, 2 to 5 times faster than mysqldump. It's not super stable yet, so we haven't been relying on it for long term backups, but doing a "mydumper to grab a schema on live, rsync down to laptop, myloader to import" it's been a big time saver.

"Hung eventually left Vietnam and ran his own photo shop in San Francisco, where he met former AP photographer Horst Faas in 1998, according to the San Francisco Examiner. 'They paid me $10 a picture,' Hung told Faas. 'It could support my whole family for one month.' A selection of Hung’s photos follows."

https://access.redhat.com/support/policy/updates/rhs

Note that the Red Hat Gluster Storage product has a defined support lifecycle through to 31-Dec-24, after which the Red Hat Gluster Storage product will have reached its EOL. Specifically, RHGS 3.5 represents the final supported RHGS series of releases.

For folks using GlusterFS currently, what's your plan after this year?