On 06/16/2016 10:47 AM, Per Jessen wrote:
Anton Aylward wrote:
On 06/16/2016 02:25 AM, Per Jessen wrote:
One thing to look into is - why aren't those files being cached? That would appear to be because the device is network attached. I am still working on this.
Cached where?
Locally, in RAM. Like any other filesystem. Afaict, filesystem cache doesn't work for filesystems on iSCSI, maybe due to the access semantics or some such. NFSv4 seems to be cached though. NFSv4 also seems to be quite a bit faster than iSCSI. Will have to investigate.
Please do. It seems backwards to me. Yes, NFS and iSCSI have different semantics as far as 'sharing' goes. The kernel knows about when its using client-side NFS and that its not a file system like ext4/BtrFs/ReiserFS no matter what the server thinks is on its disk. Local filesystems like those have their own driver-level caching for inodes, never mind the system inode cache. How tunable they are is another matter :-) https://www.usenix.org/legacy/events/fast04/tech/full_papers/radkov/radkov_h... I've not used iSCSI and don't plan to.
So comparing a single server with the BigName sites like Wikipedia isn't fair.
That was a typo, s/Wikipedia/wikimedia/. I wasn't comparing to other sites, just other apps running on the same server.
Ah, right. Have you looked into such things as whether those two packages use things like "memcache()"?
Finally, I'd point out that the MediaWiki code used by Wikipedia is available for inspection. If there's magic smoke in there you can see it. I've not looked at or for the Wordpress code but its there.
Sure, it's all there, also the processwire code, but there's little point in looking much at it when I want to fix the environment, not the application.
For starters, the developer has now enabled caching in processwire,
What kind of caching is that?
which has reduced processing time by 75%, that's good enough. Maybe they'll reduce the images too and the whole thing becomes quite workable :-)
I not that at https://blog.crazyegg.com/2013/12/11/speed-up-your-website/ it mentions that the client can cache images, but its still worth while to re-size the images on the store so that the server sends images that the client doesn’t have to spend time resizing. There's another advantage to this: smaller images also take up less client-side cache.That means they are more likely to be retained. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org