Fork me on GitHub

pnjokes, awesome mod. But it does not like pnrender.  Bottom

Go to page [-1] 1 - 2:

  • Quote


    call me crazy, but maxdev runs pnrender, and the mods i want just fine.

    ..haha..well.. :) ..I would think it would be called mdRender or something like that.. considering the prefix "PN" is PostNuke..

    aannnyywaayyy..

    as mhalbrook has mentioned, MD-Pro is likely using the older (.726) codebase.. pn.750 is a fairly major step forward in the development of the PN app.. the removal of global variables, DB optimization, XTE integration and a large step towards XHTML compliant output.

    ..sure, sure, some apps are going to require some very minor upgrades to fit the mold, but inevitably, it builds a much, much stronger, secure application and paves the path to the much anticipated pn.8.

    of course the choice is yours.. wink

    Good luck.. & take care!!
    -IR
  • I've taken a quick look at the module and the error 'An error occurred while loading the module' is caused by the module author not being certain what the module is actually called. Most of the time the module is referred to as 'pnjokes' but in this function the module is referred to as 'PNJokes'. To fix this particular error edit pnuser.php and change line 44 to lower case the module name.

    It also seems that the version file has PNJokes rather than pnjokes. The same mixed usage is found in the security schema meaning that you may encounter problems should you need different permissions for this module.

    .726 and earlier was a little more forgiving to these inconsistencies. Part of the optimisation of .750 was to reduce the overhead in loading a module. For example the pnModAPILoad API in earlier versions called the database to get information it needed to load the module. In .750 this API simply reuses information from pnModGetInfo.

    The effect of these changes is that PN .726 base install takes 42 queries to render the front page, PN .750 this is down to 38 (most optimisations are targeted at API compliant modules), mdpro 1.07rc1 (after removing the extra blocks not supplied with PN by default e.g daily archive, subjects etc.) takes 68 queries.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • markwest

    I've taken a quick look at the module and the error 'An error occurred while loading the module' is caused by the module author not being certain what the module is actually called. Most of the time the module is referred to as 'pnjokes' but in this function the module is referred to as 'PNJokes'. To fix this particular error edit pnuser.php and change line 44 to lower case the module name.

    It also seems that the version file has PNJokes rather than pnjokes. The same mixed usage is found in the security schema meaning that you may encounter problems should you need different permissions for this module.

    .726 and earlier was a little more forgiving to these inconsistencies. Part of the optimisation of .750 was to reduce the overhead in loading a module. For example the pnModAPILoad API in earlier versions called the database to get information it needed to load the module. In .750 this API simply reuses information from pnModGetInfo.

    The effect of these changes is that PN .726 base install takes 42 queries to render the front page, PN .750 this is down to 38 (most optimisations are targeted at API compliant modules), mdpro 1.07rc1 (after removing the extra blocks not supplied with PN by default e.g daily archive, subjects etc.) takes 68 queries.

    -Mark


    Thank you very very much. :P
  • markwest

    The effect of these changes is that PN .726 base install takes 42 queries to render the front page, PN .750 this is down to 38

    Xdebug says something different on my localhost... 57 *adodb_mysql->execute for standard 750rc3
  • The latest release candidate is RC4 not RC3. Also the figure is based on the anonymous user not the logged in admin user which will generate additional calls for the pending content stuff in the main menu block amongst other things. In addition there's two queries that go away after the first use of administration->settings based on some non-existent module variables which get set after the first time. For the logged in admin user I count 46 queries.

    My very simple tests are not based on any RC but on the full release build in cvs which contains a few additional fixes. I simply run the installer and add some code the execute method of adodb to count the queries. From pnadodb.inc.php we have

    Code

    function &Execute($sql,$inputarr=false)
        {
            static $count;
            $count++;
            echo "$count queries - $sql<br /><br />";
    ....


    I 99% sure that all adodb executions go through this function. This testing was done on my work machine where I don't have dbg installed but all tests where run in the same environment so the results are comparable.

    The test setup is a basic 750 install from cvs (what will be the final build) using default settings and blocks (extralite theme). The md-pro install was a base install with the all extraneous blocks removed (to match the PN setup) and the theme changed to extralite. This should be as identical as the two products can get.

    Output from theses simple tests (PN ones anyway) can be seen here (not logged in) and here (admin user logged in).

    -Mark

    --
    Visit My homepage and Zikula themes.
  • In the interests of fairness I redid the same tests again for mdpro 1.07rc1 and found that my 68 queries statement was the admin user logged in for md not the anonymous user so I wasn't quite comparing like with like. Apologies for that it was a mistake on my part.

    However the base install of mdpro for the anonymous user is still 55 queries compared to postnuke's 38 queries - still a significant difference. To create this mdpro test site I installed mdpro 1.07rc1 and changed the theme to extralite, removed the reminder, subjects, mdmenus and daily archive blocks, removed the two default news articles and, lastly flushed the sessions table. The sessions table flush was required since the daily archive block uses a session var as storage mechanism. This creates as close to two identical installs as is possible.

    Lastly don't treat these simple little tests as definitive benchmarks. Firstly they only look at one aspect - SQL queries. There are other issues for performance besides the number of queries. Secondly this compares mdpro 1.07 RC1 against PN .750 at later than rc4 so this isn't necessarily a fair test but since mdpro doesn't have a public cvs then it's the only test that could be done.

    For proper bench marking use an approrpiate setup; one workstation, one server - cleanly imaged (e.g. ghost, drive image etc.) after each test. In addition use an appropraite tool to benchmark the entire process e.g. apache bench.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Postnuke is the good one and MD is the evil one.... You are saying that MD is slow, bad etc but compare also what PN and MD can do. I can make AT themes to look as I want in no-time, making a Xanthia theme took me more time and I't was hard to make it look as I wanted to (more blocks areas etc...) + there is a lot of AT themes. Number of queries doesn't make PN better than MD-Pro or any other CMS. I'm not using... minisite which makes about 7 queries, I'm use something slower, but I't can look and work as I want.
  • Riklaunim

    Postnuke is the good one and MD is the evil one.... You are saying that MD is slow, bad etc but compare also what PN and MD can do. I can make AT themes to look as I want in no-time, making a Xanthia theme took me more time and I't was hard to make it look as I wanted to (more blocks areas etc...) + there is a lot of AT themes. Number of queries doesn't make PN better than MD-Pro or any other CMS. I'm not using... minisite which makes about 7 queries, I'm use something slower, but I't can look and work as I want.


    Please don't put words in my mouth..... My comparison was a simple one - it's contains neither opinion nor recomendation. That you will have to make your own mind up on. All I ask is that you re-read what I said and the objectivitiy with with the tests were made and apply the same objectivity yourself.

    Since you want to add opinion into things then take a look at your own post about the speed of mdpro 1.07rc1. Looks like your comments here echo my simple little tests as do your own performance tests.

    You mention what you can do with AutoTheme. AutoTheme is available for PN so no difference there. PostNuke has Xanthia and pnRender so again a templating solution available supplied with the package.

    But Fine... add AutoTheme to a postnuke .750 install and then re-run the same tests. Let me know the results. Since AutoTheme will add exactly the same overhead to both then I would expect the end results to show the exact same difference.

    All we did is take two products that are equal in terms of what is taken to build a particular page - one takes less SQL queries to do the same job than the other.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Code

    Notice: Use of undefined constant host - assumed 'host' in /home/downloadcenter/www/html/includes/mysql.php on line 13

    Notice: Use of undefined constant user - assumed 'user' in /home/downloadcenter/www/html/includes/mysql.php on line 14

    Notice: Use of undefined constant pass - assumed 'pass' in /home/downloadcenter/www/html/includes/mysql.php on line 15

    Notice: Use of undefined constant name - assumed 'name' in /home/downloadcenter/www/html/includes/mysql.php on line 16

    Notice: Use of undefined constant prefix - assumed 'prefix' in /home/downloadcenter/www/html/includes/mysql.php on line 26

    error reporting.... :First I have to download postnuke...

Go to page [-1] 1 - 2:

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