Fork me on GitHub

Watch

GitHub Core

Show your support for Zikula! Sign up at Github account and watch the Core project!




GitHub Modules

Forum Activity

Forum feed

» Visit forum | » View latest posts

speed  Bottom

  • I am a newbie with postnuke, and I am VERY impressed with all the features and opportunities of postnuke. I see a lot of fantastic opportunities.

    But, I have an objection to postnuke. That is, speed. There is for instance a small Danish newspaper website, made with postnuke, at which it take nearly 30 sec. to open their news page. On my laptop (700 MHz, 128 Mb RAM), it takes app. 10 sec. to go from one page to another. What I fear is that if I spend a lot of time on building up a good website, I will end up with a website which is so slow that it is problem.

    So, my question is. Isn't it possible to make postnuke faster?

    I am sorry to criticise this good project, and, unfortunately, I am not myself capable of contributing to any amendment of the project. But, anyhow, I think it is an important issue for the future of the project.

    Flemming
  • Yeah .721 has compression, are you using a dial-up connection?
  • bharvey42

    Yeah .721 has compression,

    Thank you, it speeds up my laptop installation considerably. Now, I think I dare use postnuke.

    are you using a dial-up connection?


    No, dsl 265/128.

    But, still I think speed is important. Let me just remind you of netscape6.0 and mozilla....

    Flemming
  • Is that what you are using to view the pages?
  • What are the specs for your webhost or are you running a server with your laptop? Also what operating system is on your laptop.
  • The main criteria for speed -on the PostNuke side- is how long it takes to generate the HTML output. That's something you can test with ApacheBench (ab) or other web stress tools.

    The rest is rather independent of PostNuke itself, and is a matter of :
    - optimising your graphics, CSS and javascript files, etc.
    - producing "clean" HTML, so that browsers can parse it rapidly on the client side
    - using compression on the webserver (mod_gzip), or if it's not available or activated for PHP scripts, enabling compression in your php.ini file, or if you can't modify that, enabling it in the script itself
    - (if you own the server) tuning your server and network to eliminate bottlenecks
    - (if you own the server) using PHP Accelerator or similar tools to avoid recompiling your scripts on each request

    After that, you can return to PostNuke and start playing with cache control to improve cacheability on the client side (and/or intermediate caches), introduce caching of blocks, modules and pages in PostNuke, generate ETags and Last-Modified headers and send back 304 Not Modified status codes, etc.

    Along with that, you can start splitting off your webserver into two, so that dynamic requests are handled in the back-end server, and the front-end server handles static content and feeds the output back to the client, etc.

    In short, PostNuke itself can only provide part of the answer in terms of speed - the rest is up to what you do with it, and external factors.

    See the performance tips at http://mikespub.net/tools/postnuke/ for some figures...
  • i ce no performance probs @ eckerl.de, but i have cleaned up some modules of tableopen stuff, maybe the lack of tables speeds up the rendering speed in the browser.
    As well my template has no root table containing subtables.

    Greets
    base
  • Thannk you, for your tips, and to all others, too. I must admit that they are a bit beyond my capability. But, now I know where to find them. Compression was enough right now.

    Flemming

This list is based on users active over the last 60 minutes.