long initial load time when accessing 1.1 remotely

[Capitan]

Great program,

I have a problem when I initially connect to 1.1 remotely.  It has the "loading" dialogue for a long time, sometimes several minutes.  After it finishes, everything works quickly and easily.

Any ideas?

[Karl]

Try using the minify function. Minify speeds up loading time really very much.

See here: http://forums.opengoo.org/index.php?topic=640.0

[Capitan]

Nothing for me:(

cat access.php
<?php
/* This script defines which tools will be publicly accessible.
 * If you need to further refine permissions you will need to
 * use server configurations like a .htaccess file for Apache.
 */ 

return array(
   'combine.php',
   'checklang.php',
   'minify.php',
);

?>


what did i do wrong?

[Karl]

What did you do and what errors do you get?

Please refer to this thread: http://forums.opengoo.org/index.php?topic=640.0

Maybe the OpenGoo staff can help you.

[ignacio]

Hi Capitan,

You don't need to run the minify process unless you make modifications to the CSS or Javascript (excluding language javascripts). You only need to define a couple of contants in the config.php file called 'COMPRESSED_CSS' and 'COMPRESSED_JS', set as 'true'.

I'm thinking of creating a config option (on the Administration section) to enable this.

[Capitan]

I don't get any errors, I just see no difference in speed.  What do I need to do?  It still takes 2-3 minutes, at least, at "loading" after I log in.

[ignacio]

Another thing you can do is set the USE_JS_CACHE option to true in the config file.

2 or 3 minutes is too long a time for loading. What is your internet connection download bandwidth? And how about the server's upload bandwith?

[Capitan]

It depends where I am logging in from.  Sometimes it's cable modem speed, other times 20-50k/s.  I only notice it when I log in remotely.

Once the initial login screen passes, everything is fast.  It's just then.

[Capitan]

I started to get a lot of:
error -1 transaction aborted

after I did that javascript thing, so I removed it.

[Capitan]

Actually, it seems to be more like 10 minutes that it sits at "Loading" after signing in, even when I have a fast internet connection like right now.

Once it finally goes past that, everything is fast.

It just shows the animated "loading" graphic for like 10 minutes.

[ignacio]

I've just measured my loading times on a 2 Mbps connection (1600 kbps according to speedtest.net ~ 200KB/s). This is what I got:

• No minify ~ 50 s
• Minified JS and CSS ~ 23 s
• Minified JS and CSS with USE_JS_CACHE ~ 15 s

So if you have a 20 KB/s connection you would have to multiply this times by 10, which gives you 8m20 s, 3m50s and 2m30s respectively.

So a 10 minute wait for loading OpenGoo on a 20 KB/s connection when nothing is minified would be normal, but when minified it shouldn't take that long.

[Capitan]

This is how my access.php should look, right?

<?php
/* This script defines which tools will be publicly accessible.
 * If you need to further refine permissions you will need to
 * use server configurations like a .htaccess file for Apache.
 */

return array(
   'combine.php',
        'checklang.php',
        'minify.php',
);

?>

[ignacio]

Yes, but let me reimnd you that OpenGoo comes with the minified CSS and JS and you don't need to run the public/tools/minify.php file unless you modify any javascript (excluding language javascripts) or CSS file. You only need to define these two constants in config/config.php:

Code: [Select]

define('COMPRESSED_CSS', true);
define('COMPRESSED_JS', true);

Additionaly, you could add this following constant to further improve loading times, if it works on your system (I think you already said it didn't work for you, but just to keep it on the record):

Code: [Select]

define('USE_JS_CACHE', true);


[Karl]

...unless you modify any javascript or CSS file...

Does this include the language files (lang.js)?

[ignacio]

No, it doesn't include the lang.js file. The lang.js is not minified and os you can edit it without needing to run the minify process.

Thanks for pointing it out! I'll update my previous posts for future reference.