Johannes Schlüter - Comments

Wlad: Upcoming talks

nospam@example.com (Wlad) — Thu, 12 Jan 2012 13:23:59 +0100

Konnectoren ist Denglish:)? Richtiges Deutsch hat doch mehr 'K's, d.h Konnektoren?

Hanna: High Performance PHP Session Storage on Scale

nospam@example.com (Hanna) — Tue, 29 Nov 2011 19:40:57 +0100

Haha, I miss the good old time, everything was easier and slower. I like the idea of a central repository.

vlad s.: High Performance PHP Session Storage on Scale

nospam@example.com (vlad s.) — Sat, 19 Nov 2011 18:59:02 +0100

I would cut this post in half.

gggeek: High Performance PHP Session Storage on Scale

nospam@example.com (gggeek) — Fri, 18 Nov 2011 14:10:36 +0100

I remember using phplib for session management too. Those where the days!... well, actually, I was so glad when php native session management came around

Johannes: High Performance PHP Session Storage on Scale

nospam@example.com (Johannes) — Thu, 17 Nov 2011 21:41:24 +0100

Oh, the good old days. Back when my 90 MHz Pentium was good enough to host my site and MySQL 3.23 did all I needed from a database

Johannes: High Performance PHP Session Storage on Scale

nospam@example.com (Johannes) — Thu, 17 Nov 2011 21:35:03 +0100

MySQL Cluster can operate in a way that all data is kept in memory. This makes it extremely fast. MySQL Cluster can also be configured to store data on disk. With this it's still a MSQL Cluster requirement to have enough memory so it can keep indexed fields (the session IDs in this case) in memory. Now session ids aren't that big that even with cheap hardware and only a few gigs of RAM you should be able to handle quite a lot users. Switching off backing storage on disk for sessions is also fine as there usually is no need to persist them. Cluster can protect them from failing hardware by making sure there are two copies all the time on different machines so only time you would loose them is if larger parts of the cluster shuts down. And as a remark: It's always a good idea to have enough RAM to be able to keep the complete working set in memory, for all databases

Kai Voigt: High Performance PHP Session Storage on Scale

nospam@example.com (Kai Voigt) — Thu, 17 Nov 2011 21:22:08 +0100

MySQL Cluster can use disk based storage for older records (LRU paging), HBase does the same.

Steven Roussey: High Performance PHP Session Storage on Scale

nospam@example.com (Steven Roussey) — Thu, 17 Nov 2011 21:20:16 +0100

So a persons session kept for long periods of inactivity must be kept in RAM (MySql Cluster works that way)?

Kai Voigt: High Performance PHP Session Storage on Scale

nospam@example.com (Kai Voigt) — Thu, 17 Nov 2011 20:26:55 +0100

Cool article. I recall the fun time when we developed PHPlib and the session code. And also great to see to attach MySQL cluster to it as a low latency storage. Did you consider using HBase as another backend? I'd like to help you on this.

Ernesto: mysqli_result iterations

nospam@example.com (Ernesto) — Thu, 17 Nov 2011 12:19:56 +0100

that MYSQLI_USE_RESULT was exactly what i was looking for, thanks!

Yannick K.: mysqli_result iterations

nospam@example.com (Yannick K.) — Mon, 14 Nov 2011 18:39:48 +0100

Nice ! Thank you !

nIcO: References and foreach

nospam@example.com (nIcO) — Wed, 26 Oct 2011 14:40:37 +0200

Excellent diagrams that make the problem easy to understand. Thank you !

James A: Features in PHP trunk: Array dereferencing

nospam@example.com (James A) — Wed, 12 Oct 2011 17:39:55 +0200

like this? echo false ?: 'ok'; // print ok

Ulf: mysqlnd_qc and Symfony2

nospam@example.com (Ulf) — Sat, 08 Oct 2011 00:54:26 +0200

BTW, there should be a basic cache monitor in the qc repository... a little web script

Johannes: Do not use PHP references

nospam@example.com (Johannes) — Fri, 07 Oct 2011 23:45:30 +0200

No it won't.