Re: php file loading performance
- From: "_q_u_a_m_i_s's" <quamis@xxxxxxxxx>
- Date: Wed, 30 Jan 2008 07:30:35 -0800 (PST)
On Jan 30, 1:08 pm, Iván Sánchez Ortega <ivansanchez-...@rroba-
escomposlinux.-.punto.-.org> wrote:
Blitzen wrote:
Does the sapi/cgi php have an option to keep all the php files it's called
in its memory space and never touch the disk or call open( ) again?
Why bother? The OS will have that file cached to memory...
--
----------------------------------
Iván Sánchez Ortega -ivansanchez-algarroba-escomposlinux-punto-org-
"The difference between pornography and erotica is lighting."
- Gloria Leonard
You may mount the apc temp path to a ramdisk(so the files will really
be in memory).
I dont know how apc is implemented, but most probably it will only
"intercept" opened files, but it will not disable the fopen() from php
with his own filehandlers. You may ask a question on the apc forum...
but it would be kinda dificult(read: needs lots of hacking, prone to
future bugs) to replace the fopen from php with an internal open from
the apc...
If you need fast file acceses, then disable atime when mounting the
partition with the php & apc cache scripts, and put them in a
ramdisk . I do belive that moving the apc cache to a ramdisk would be
enough, as it should check if a file had changed by only checking
filemtime(modify time).
Also pay attention to the used filesystem. from what i remember ext3
was faster for big files, while reiserfs was faster for smaller
files(this should be the case for the cache & php files). The only way
to reliable determine this is to test it yourself, there are many
flame wars started from benchmarking the file systems, with no real
conclusion in my opinion.
.
- References:
- php file loading performance
- From: Blitzen
- php file loading performance
- Prev by Date: mkdir not working
- Next by Date: Re: mkdir not working
- Previous by thread: php file loading performance
- Next by thread: Statistics for SHOW TABLE
- Index(es):
Relevant Pages
|
