XCache is a fast, stable PHP opcode cacher that has been tested and is now running on production servers under high load. It is tested (on linux) and supported on all of the latest PHP cvs branches such as PHP_4_3 PHP_4_4 PHP_5_0 PHP_5_1 PHP_5_2 HEAD(6.x). ThreadSafe/Windows is also supported. It overcomes a lot of problems that has been with other competing opcachers such as being able to be used with new PHP versions. please add this to portage :) thanks Saurabh
Created attachment 97671 [details] Ebuild for xcache 1.0.1 (should be usable for all releases, excluding RCs)
Created attachment 97672 [details] Ebuild for xcache 1.1_rc1 (should be usable for all RCs, don't know whether the hardened thing still works)
Created attachment 97674 [details] Ebuild for xcache svn trunk (don't know whether the hardened thing still works)
Created attachment 97675 [details] Patch for xcache to work with hardened-php again, found it somewhere on their wiki iirc, but don't know if it works/applies with current releases or if it is still necessary, it worked with 1.0.0
I attached all ebuilds for xcache I have. All do compile on both of my machines (with all useflags enabled), but I only tested with php5 (so it was dev-php5/xcache), but I don't see a reason why they should not work with php4 (maybe they need different blockers for the other opcode caches, if those blockers are even required) They were some of my first ebuilds, so please don't kill me if I did something terribly wrong. :p
Thanks a lot man !! The first ebuild I tested, and it works gr8 :)
(In reply to comment #6) > Thanks a lot man !! The first ebuild I tested, and it works gr8 :) > The svn ebuild works good on ppc platform :)
The USE-flags seems completely useless to me. Just enable all options per default. Introducing local USE-flags here seems to be overhead.
Created attachment 101218 [details] xcache-1.1_rc2.ebuild Cleaned up the ebuild, removed useless USE-flags, included IUSE=test, which I'm not sure, if it is working.
1.1rc1 works fine here on x86
the ini is changed since 1.2 Ini Settings Changes ======== * new: xcache.stat = On * new: xcache.coverager = Off * chg: xcache.coveragedump_directory default to "" * del: xcache.coveragedumper = Off see http://trac.lighttpd.net/xcache/browser/trunk/NEWS
Created attachment 103712 [details] Ebuild for stable xcache versions (1.1.0 in this case)
Created attachment 103713 [details] Ebuild for xcache release candidates (1.2.0_rc2 in this case)
Created attachment 103714 [details] Ebuild for xcache svn trunk
Added updated ebuilds... (In reply to comment #9) > Cleaned up the ebuild, removed useless USE-flags, included IUSE=test, which I'm > not sure, if it is working. Thanks for the cleanup -- I didn't even notice how I messed up the indentions. :\ Regarding test: --enable-xcache-test (which, btw, is according to the configure help "FOR DEVELOPERS ONLY!!!") currently doesn't do anything as far as I see (I compared the output of make, make test and make xcachetest -- no difference). The usual make test is broken and says "ERROR: Cannot run tests without CLI sapi.", make xcachetest fails as well as it seems to require the whole PHP testing framework -- adding support for that is useless IMO. That's why I removed the test use flag again. (In reply to comment #11) > the ini is changed since 1.2 > > Ini Settings Changes > ======== > * new: xcache.stat = On > * new: xcache.coverager = Off > * chg: xcache.coveragedump_directory default to "" > * del: xcache.coveragedumper = Off > > see http://trac.lighttpd.net/xcache/browser/trunk/NEWS Yup, added them to the ebuild. :)
1.2.0_rc2 compiles and works fine on sparc. Please add ~sparc :)
Imported to tree, thanks :)
(In reply to comment #14) > Created an attachment (id=103714) [edit] > Ebuild for xcache svn trunk > I have had several issues with this ebuild. Over at xcache they tell me the 2.0-dev release on which this ebuild is based is nowhere near stable. On their website (http://trac.lighttpd.net/xcache) they recommend v1.0.x for php4 and 1.2.x for php5
(In reply to comment #18) > (In reply to comment #14) > > Created an attachment (id=103714) [edit] > > Ebuild for xcache svn trunk > > > > I have had several issues with this ebuild. Over at xcache they tell me the > 2.0-dev release on which this ebuild is based is nowhere near stable. On their > website (http://trac.lighttpd.net/xcache) they recommend v1.0.x for php4 and > 1.2.x for php5 > the issues I had were with php4.4.4-p18-gentoo
(In reply to comment #18) > I have had several issues with this ebuild. Over at xcache they tell me the > 2.0-dev release on which this ebuild is based is nowhere near stable. On their > website (http://trac.lighttpd.net/xcache) they recommend v1.0.x for php4 and > 1.2.x for php5 I don't see a problem here. In the tree there is only 1.2 for php5 which is what upstream recommends. I created and attached the svn ebuild because some months ago the releases were not done that often and there were several bugs which were fixed in svn trunk. So, simply don't use -9999 if you don't need it. Use the 1.2 ebuild in the tree for php5. I'm not sure what to use for php4 though. On their wiki they say that 1.0 is recommended, but they don't explicitly state that 1.2 removes or decreases support for php4. So I'd try 1.2 here as well. Going to ask moolight later though.
I just asked moolight (xcache developer), he recommends 1.2.0 for php4 as well.
(In reply to comment #21) > I just asked moolight (xcache developer), he recommends 1.2.0 for php4 as well. > thanks but emerging dev-php5/xcache will do little to speed up my php4 configuration
> thanks but emerging dev-php5/xcache will do little to speed up my php4 > configuration But that's no gentoo-related problem. Upstream recommends 1.2 for both php4 and php5 and so it should work. If it doesn't, please report a bug at http://trac.lighttpd.net/xcache/report Maybe you could also try upgrading to php5. It was released almost three years ago and probably contains many fixes which are not present in php4.
(In reply to comment #23) > > thanks but emerging dev-php5/xcache will do little to speed up my php4 > > configuration > But that's no gentoo-related problem. Upstream recommends 1.2 for both php4 and > php5 and so it should work. If it doesn't, please report a bug at > http://trac.lighttpd.net/xcache/report > Maybe you could also try upgrading to php5. It was released almost three years > ago and probably contains many fixes which are not present in php4. > I think I'm missing something here. I simply wanted to point out that 1.2 isn't packaged for php4 so I can't use it unless I install it from source which is sort of defying the point of gentoo
> I think I'm missing something here. I simply wanted to point out that 1.2 isn't > packaged for php4 so I can't use it unless I install it from source which is > sort of defying the point of gentoo Sorry, misunderstood that. Of course, dev-php5/xcache installs xcache.so into the php5 extension dir and is only usable by php5. Currently there is no dev-php4/xcache, maybe I'll test that and add the ebuild for php4 as well. For now, as you already seem to have used the ebuild xcache-9999 from this bug, just do the same with xcache-1.2.0.ebuild (from the tree) and use it in an overlay in dev-php4.
(In reply to comment #25) > > I think I'm missing something here. I simply wanted to point out that 1.2 isn't > > packaged for php4 so I can't use it unless I install it from source which is > > sort of defying the point of gentoo > Sorry, misunderstood that. Of course, dev-php5/xcache installs xcache.so into > the php5 extension dir and is only usable by php5. > Currently there is no dev-php4/xcache, maybe I'll test that and add the ebuild > for php4 as well. > For now, as you already seem to have used the ebuild xcache-9999 from this bug, > just do the same with xcache-1.2.0.ebuild (from the tree) and use it in an > overlay in dev-php4. > thanks for the suggestion. Works like a charm!
