A couple of stats so far against 121

[John Cox]

I thought it would be interesting to see the progress so far, so from
a stock 121 install with the profiler installed:


121:

0.225426912308 <- Page execution time
(
[memory_usage] => 5.26 MB
[peak_memory_usage] => 5.54 MB
[memory_available] => 32M
)

88 Files included

88 Queries executed


SailFish:

0.190447092056 <- Page execution time
(
[memory_usage] => 4.48 MB
[peak_memory_usage] => 4.68 MB
[memory_available] => 32M
)

54 Files included

21 Queries executed.

We are making some progress in two weeks;) I think we can cut the
memory down to around 3M which is still probably a little on the high
side. Perhaps we can make use of the load defines or something,
haven't dug in yet. There should be something that we can do to
improve this though.

As far as the queries, I know I can cut those in half, and a lot of
them are doing full text scans, which will cut page execution time
down.

Well on our way to a standalone application builder:)

[John Cox]

On Jun 21, 9:16 am, John Cox <john.cox...@gmail.com> wrote:

>
> SailFish:
>
> 0.190447092056 <- Page execution time
> (
>     [memory_usage] => 4.48 MB
>     [peak_memory_usage] => 4.68 MB
>     [memory_available] => 32M
> )
>
> 54 Files included
>
> 21 Queries executed.

heh, Just by adding adodb-lite instead of adodb check this out:

0.145724058151Array
(
[memory_usage] => 3.33 MB
[peak_memory_usage] => 3.53 MB
[memory_available] => 32M
)

Should we use this instead?

[jojodee]

On 21 June 2010 23:27, John Cox <john.cox.ky@gmail.com> wrote:

heh, Just by adding adodb-lite instead of adodb check this out:

0.145724058151Array
(
   [memory_usage] => 3.33 MB
   [peak_memory_usage] => 3.53 MB
   [memory_available] => 32M
)

Should we use this instead?

I thing this is the same extension I referred to earlier in our performance discussion (C based). I think it looks fine, and licence wise it seems OK. Certainly size and performance considerations suggest we should go with it. However, I'm not the expert here and dont' know if there are some downside considerations or not. What comes to mind is maintenance - is it regularly maintained and do we need to do adjustments? Having it in PHP is an advantage for me then, over having to revive C coding skills which would be the one disadvantage for me.

[John Cox]

You may well have:)  

I am taking a look at it now, but there is a problem with the genID function.  There is an extension to revive it, but it doesn't behave quite the way that the majority of code wants.  I am giving it a go to get it working though...  

I'll push down my profiler changes (real real rough) as I am going to be on the road all week and won't look at anything else until the weekend...

Enjoy your trip:) 

[John Cox]

On Mon, Jun 21, 2010 at 12:17 PM, jojodee <joj...@gmail.com> wrote:

I thing this is the same extension I referred to earlier in our performance discussion (C based).

I think we are talking about two separate extensions.  Here's the adodb-lite extension:

http://adodblite.sourceforge.net/

Looks like a somewhat dead project, but to cut 1M of memory off the page, not bad, if we can get the genID working, which right now is a big if.  I got it working to a point, but then it dies on config vars.  Normal page loads work fine.

Also, I am going to log a couple of bugs.  I don't think we are staying logged in right now.  Also, there's a weird problem on the installer that needs the "all access" checkbox on privs to be checked.  I think I caused both of these somewhere along the way.  No biggie right now though.

I'll clean up the profiler this weekend (maybe) and get the pull menu working for it.  Also, I'll add the config vars to turn certain things on and off.  

One thing if you have the chance to look at (no biggie if you don't), in xarTemplate, I can't figure out how to push the variable into an array.  I am generating the keys correctly, but the value is being overwritten with array_push .  I think it's around line 500 - 700 where the tplData is being generated.  It was the old code that I threw in to get all variables to the templates to display.  I left a comment to fix it one day;)

Enjoy your trip:)