Ditto, I took his discrete math course at NCSU in 1998. It was mainly taught by Tiffany Barnes day to day (who was also nice and a great explainer), but Bitzer was often present and always smiling and jovial.
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?
Our vector implementation is fully compatible with the syntax for vector fields and comparison functions in MySQL 9 -- we have carefully backported all the changes to our version of MySQL 8 to ensure full backwards and forwards compatibility. The index syntax is specific to PlanetScale because the open-source MySQL 9 preview does not yet have support for ANN indexes on vector columns, but we're committed to being as compatible as possible in the future and to minimize fragmentation. I do agree that fragmenting the ecosystem is not great!
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.
> 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.
Yes, that is true. But most high-traffic websites will cache static files such as CSS files and images, using a reverse proxy (e.g. Varnish, a CDN, or usually both). So I don't think this is a real problem, most of the time (99.9%?), a request for a static file will not hit Apache.
I'm not saying mod_php is better for all scenarios, of course, but I think it can be ok.
I tend to agree with you - using in "default" setup with mod_php and mpm_prefork is known to be far from optimal (still fine for blog about you and your cat).
With reverse proxy in front of such setup is - much better in terms of performance. For shared hosting - yet again, may be not optimal if one needs to support multiple system users.
Yes, but MariaDB, mostly DIY on localhost (various test & live VMs I manage).
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."
Amazing find. That mention of the Examiner led to the June 22, 1998 edition, front page of the Style section by Vietnam veteran Edvins Beitiks ("Ed"), "'Requiem' for A War, An Era":
"And at each exhibit, Faas has been approached by people with their own memories, people wanting to talk. In San Francisco, he was surprised by Jimmy Lo Hung, who took pictures for AP as a 12-year-old during the Tet offensive and now runs his own photo shop on Ninth Street.
Hung had brought a picture of himself in a helmet with PRESS across the front, and a laminated story headlined 'Boy, 12, in Dangerous Jobs'. 'They paid me $10 a picture,' he said, 'and that was big money in Vietnam. It could support my whole family for one month.'
Hung lost all his pictures and negatives when the North Vietnamese invaded the South. 'I only had a few minutes to escape,' he said, remembering that 'I was pulled aboard a helicopter filled with soldiers. They held my leg while it took off. So many soldiers trying to get on… some didn't, some dropped down.'
Faas, sitting beside Hung, said 'This kid, I didn't even know he was alive. I'm happy, really happy, to see him.'"
I wonder if the lab might have been Newtec Color Lab Inc at 122 9th St which appears to have been run by a Jimmy H Lo (Jun 1956–Jan 2018). There's also a tribute to Horst Faas at the Vietnam Reporting Project here: https://vietnamreportingproject.org/2012/05/remembering-hoor...
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?
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.