Tag Info

New answers tagged

0

Yes, you can use APC to store the result in RAM. You just need to install APC module, and then add code to store /fetch resized versions inside APC using apc_store() and apc_fetch() functions.


0

You cannot have information about L1, L1d & L1i cache from dmidecode. Its just gives you the total L1 L2 & L3 cache information. lscpu is a neat command to give you the cache information. lscpu|grep cache You can also have more information in /sys/devices/system/cpu/


1

I believe you'll want to add the http method to fastcgi_cache_key or possibly only include GET in fastcgi_cache_methods.


2

Yes, the variable is $request_method and that's what you will want to add to fastcgi_cache_key. This will cause GET and HEAD requests to be cached separately.


3

I do not think that your ISP is caching anything in this regards, here are the reasons: To serve YOUR certificate with YOUR thumbprint, they need to have access to YOUR private key ISP's usually do not cache SSL traffic ISP's escpecially do not cache SSL traffic on non-standard ports So this seems to be an issue with your own server. Try rebooting it, ...


0

To answer further to the crash issue, Just for the benefit of the community - this is something unique which was causing havoc for me and I didn't find any instance of this situation asked or answered before in my extensive seach on this issue. The Issue for getting frequent Internal server errors was that - I had PHP 5.4.27 and Zend Opcache was installed ...


0

It is a very probable cause of crashing. If your software do not use apc key cache, but only opcache, then upgrade to Zend OPcache should just work. If you use apc key cache, then there will be some programming involved to migrate to some other key caching solution like memcached. From php 5.4 and up most benchmarks show a reasonable speed up using Zend ...


0

I can imagine what would happen if you tried to run two opcode caches simultaneously. It looks a lot like this. So you should run one opcode cache, and one only. And, this may surprise you, but you need to get rid of APC, and keep Zend OPcache. The reason is that APC is very, very crashy. It alone may well be the cause of your PHP crashes, as it was for ...


0

You should only use APC with your PHP 5.4 installation. APC contains both user variables caching and opcode caching for PHP files. APCu is meant to complement PHP 5.5's integrated opcode cache by adding user variables caching. So, you should uninstall your APCu, it might cause the problems you describe.


1

fsfreeze uses the FIFREEZE ioctl. Here is the kernel function call chain: ioctl_fsfreeze() freeze_super() sync_filesystem() From the comment above the sync_filesystem() function: "[w]rite out and wait upon all dirty data associated with this superblock [filesystem]. Filesystem data as well as the underlying block [will be written."


2

It seems like your rootfs (/) is at 100%! Try cleaning it up first, maybe try yum clean all.


2

You're out of space. Free up some or get a bigger disk.


1

You can do this using Sysinternals RAMMap: http://technet.microsoft.com/en-gb/sysinternals/ff700229.aspx The following link gives this example: If you want to check for performance regression tests if your cache is filled you could execute rammap C:\temp\ram.xml to get a nice xml file which shows which files are being in the cach now. The ...


1

Run this function as root on your linux server: apachectl graceful works for me on debian. If that is not working you can try parameter -k apachectl -k graceful error messages in dutch chrome: Fout met SSL-verbinding error message in english chrome: Error with SSL connection


0

Note that Last-Modified headers are weak cache headers. The current preference is to use Cache-Control headers. Google has a good article on this. Optimize Caching Expires and Cache-Control: max-age. These specify the “freshness lifetime” of a resource, that is, the time period during which the browser can use the cached resource without checking ...



Top 50 recent answers are included