2

There's a good chance that I'll end up running Drupal on several front-end nodes over the next six months, and I'd like to know if there is a good reason not to have a single instance of Drupal stored on Gluster. We'll be using APC, so presumably most of Drupal would end up in the local opcode cache, meaning there wouldn't be a ton of reads- am I wrong about that?

jj_aa
  • 35
  • 1
  • 1
  • 6

3 Answers3

1

Because drupal relies heavily on file_exists statements which can not be cached in APC and causes glusterfs to check with the quorum of servers to see if the file exists. So crazy horrible performance.

jozwikjp
  • 141
  • 2
1

`You can use quick-read and io-cache to improve small file performance. 3.0 release has some more optimizations for small files. But I agree with you, if these are static PHP pages, you are better off with rsync to make local copies.

0

I believe there'll be a large network overhead when Drupal asks the Gluster to give him tons of small files.

Ensure first you have a copy of all these files on each node, and then proceed.

kolypto
  • 11,058
  • 12
  • 54
  • 66
  • Umm, if he had a copy of all the files on each node, he wouldn't need GlusterFS, would he? – rodjek Dec 10 '09 at 12:50
  • He may use GlusterFS features to access files that are not so often used ;) Some file archives, for instance. – kolypto Dec 11 '09 at 09:18