Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Gonzalo Odiard]

Hi Tony,
This is a consequence of the issue pointed a few mails before in this
thread:
this tool is running in a separated process to Sugar.
That in part explain the slowness. We are discussing ways to make this
process
notify to Sugar about the activity installed, making the process itself
lighter.

Gonzalo

On Tue, Sep 1, 2015 at 1:07 PM, Tony Anderson  wrote:

> Hi, Gonzalo
>
> I am learning a lot about debugging Sugar that may be useful going
> forward. I tried enabling logging as below. However, I am not sure which
> log you are
> referring to. The only stdout was notice that the bundle was installed.
> Strangely, I did not get the normal unzip list of files. I also didn't get
> the normal
> mimetype excluded message. The Log activity log for the shell and Terminal
> activity does not show any relevant output.
>
> Tony
>
> On 08/31/2015 08:53 PM, Gonzalo Odiard wrote:
>
>> If you can enable logging (remove the comment in the line
>> SUGAR_LOGGER_LEVEL
>> in the file /home/olpc/.sugar/default/debug)
>> And install one of the activities without unset the SUGAR_PROFILE env
>> variable,
>> and send the log, maybe we can understand better what is happening.
>>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
Gonzalo Odiard
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Tony Anderson]

Hi, Gonzalo

I am learning a lot about debugging Sugar that may be useful going 
forward. I tried enabling logging as below. However, I am not sure which 
log you are
referring to. The only stdout was notice that the bundle was installed. 
Strangely, I did not get the normal unzip list of files. I also didn't 
get the normal
mimetype excluded message. The Log activity log for the shell and 
Terminal activity does not show any relevant output.


Tony

On 08/31/2015 08:53 PM, Gonzalo Odiard wrote:
If you can enable logging (remove the comment in the line 
SUGAR_LOGGER_LEVEL

in the file /home/olpc/.sugar/default/debug)
And install one of the activities without unset the SUGAR_PROFILE env 
variable,

and send the log, maybe we can understand better what is happening.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Martin Abente]

The problem caused by the race condition is that the activities were not
refreshed in Sugar activities list when updated or, not added to the list
when installed. By race condition I mean the situation where the
BundleRegistry detects changes (e.g. in ~/Activities) too early, when
activity.info is not available yet, so the bundle gets ignored. I
personally don't think is related to this issue.

Now, looking at Tony's report and Sam's confirmation that this issue is
related to the change in [1], my first guess would be that the problem is
caused by the overhead generated by initializing the BundleRegistry, and
any other sugar module imported by it, every time the sugar-install-bundle
script is executed. Note that the script runs in a different process than
the sugar shell, so the registry instance returned by get_registry() is not
the same one as the one in the shell. Having SUGAR_PROFILE set doesn't
necessarily mean the script is being executed in the same context as the
shell.

If my guess is confirmed, we should revise that change or revert it.

Refs:
1.
https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415

On Mon, Aug 31, 2015 at 9:02 AM, Gonzalo Odiard  wrote:

> I am wondering if this issue ca be related to the race condition detected
> by Martin when the file monitor detect the activity before the
> activity.info file
> is saved to disk.
>
> Martin, do you have a patch to test?
>
> Gonzalo
>
> On Mon, Aug 31, 2015 at 10:00 AM, Gonzalo Odiard 
> wrote:
>
>> Tony,
>> If you can enable logging (remove the comment in the line
>> SUGAR_LOGGER_LEVEL
>> in the file /home/olpc/.sugar/default/debug)
>> And install one of the activities without unset the SUGAR_PROFILE env
>> variable,
>> and send the log, maybe we can understand better what is happening.
>>
>> I am afraid the slowness will impact Browse even if you patch it, because
>> Browse process
>> run in a environment with the env variable set.
>>
>> One more question: the time is bigger in slower devices (XO-1) than in
>> XO-4,
>> or is independent of the hardware performance?
>>
>> Gonzalo
>>
>>
>> On Sun, Aug 30, 2015 at 7:34 PM, James Cameron  wrote:
>>
>>> G'day Sam,
>>>
>>> Adding a flag for a workaround seems like you've given up.  ;-)
>>>
>>> Wouldn't it be better to fix the problem?  As you can see from
>>> #4849 it occurs in Sugar, and only inside Terminal activity.
>>>
>>> Why is it happening?
>>>
>>> Why does it take up to 24 minutes to install Browse using Terminal?
>>>
>>> Why does it take up to 5 minutes to install in Sugar 0.98?
>>>
>>> And yet only half a second if the bundle registry is bypassed?
>>>
>>> The bundle registry can't be that slow.
>>>
>>> By understanding the problem we'll be able to say whether it is
>>> causing any other slowness of Sugar.
>>>
>>> --
>>> James Cameron
>>> http://quozl.linux.org.au/
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
>>
>>
>> --
>> Gonzalo Odiard
>>
>>
>
>
> --
> Gonzalo Odiard
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Gonzalo Odiard]

Is a good point.
Maybe we should add a dbus method to register a bundle,
and a method in the toolkit to do the call,
then this script use that method.
I didn't realized this before, because is included in the sugar module,
but we should not use jarabe here.

Gonzalo

On Mon, Aug 31, 2015 at 2:03 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:

> The problem caused by the race condition is that the activities were not
> refreshed in Sugar activities list when updated or, not added to the list
> when installed. By race condition I mean the situation where the
> BundleRegistry detects changes (e.g. in ~/Activities) too early, when
> activity.info is not available yet, so the bundle gets ignored. I
> personally don't think is related to this issue.
>
> Now, looking at Tony's report and Sam's confirmation that this issue is
> related to the change in [1], my first guess would be that the problem is
> caused by the overhead generated by initializing the BundleRegistry, and
> any other sugar module imported by it, every time the sugar-install-bundle
> script is executed. Note that the script runs in a different process than
> the sugar shell, so the registry instance returned by get_registry() is not
> the same one as the one in the shell. Having SUGAR_PROFILE set doesn't
> necessarily mean the script is being executed in the same context as the
> shell.
>
> If my guess is confirmed, we should revise that change or revert it.
>
> Refs:
> 1.
> https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415
>
> On Mon, Aug 31, 2015 at 9:02 AM, Gonzalo Odiard  wrote:
>
>> I am wondering if this issue ca be related to the race condition detected
>> by Martin when the file monitor detect the activity before the
>> activity.info file
>> is saved to disk.
>>
>> Martin, do you have a patch to test?
>>
>> Gonzalo
>>
>> On Mon, Aug 31, 2015 at 10:00 AM, Gonzalo Odiard 
>> wrote:
>>
>>> Tony,
>>> If you can enable logging (remove the comment in the line
>>> SUGAR_LOGGER_LEVEL
>>> in the file /home/olpc/.sugar/default/debug)
>>> And install one of the activities without unset the SUGAR_PROFILE env
>>> variable,
>>> and send the log, maybe we can understand better what is happening.
>>>
>>> I am afraid the slowness will impact Browse even if you patch it,
>>> because Browse process
>>> run in a environment with the env variable set.
>>>
>>> One more question: the time is bigger in slower devices (XO-1) than in
>>> XO-4,
>>> or is independent of the hardware performance?
>>>
>>> Gonzalo
>>>
>>>
>>> On Sun, Aug 30, 2015 at 7:34 PM, James Cameron  wrote:
>>>
 G'day Sam,

 Adding a flag for a workaround seems like you've given up.  ;-)

 Wouldn't it be better to fix the problem?  As you can see from
 #4849 it occurs in Sugar, and only inside Terminal activity.

 Why is it happening?

 Why does it take up to 24 minutes to install Browse using Terminal?

 Why does it take up to 5 minutes to install in Sugar 0.98?

 And yet only half a second if the bundle registry is bypassed?

 The bundle registry can't be that slow.

 By understanding the problem we'll be able to say whether it is
 causing any other slowness of Sugar.

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

>>>
>>>
>>>
>>> --
>>> Gonzalo Odiard
>>>
>>>
>>
>>
>> --
>> Gonzalo Odiard
>>
>>
>


-- 
Gonzalo Odiard
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[James Cameron]

I agree, that might be good.

An strace of sugar-bundle-install shows the huge amount of work
required to start this other instance of the bundle registry, only to
dismantle it on exit.

Alternatively, if there were a method by which sugar-bundle-install
could tell the shell that a new bundle has been installed, there would
be no need to use the bundle registry at all.

This ties in with a recent discussion about how the shell detects
activities installed by a system package manager.  Currently an Gio
inotify watch is used, and it suffers from a race condition.  It is
overkill compared to a simple notification or signal.

Also, if we trust the Gio inotify watch so much, why are we bothering with
the registry in sugar-bundle-install anyway?

Could we please switch to a SIGHUP handler and a PID file?

diff --git a/bin/sugar-install-bundle b/bin/sugar-install-bundle
index 426c220..b5580bb 100644
--- a/bin/sugar-install-bundle
+++ b/bin/sugar-install-bundle
@@ -4,10 +4,6 @@ import sys
 
 from sugar3.bundle.activitybundle import ActivityBundle
 
-from dbus.mainloop.glib import DBusGMainLoop
-DBusGMainLoop(set_as_default=True)
-
-
 def cmd_help():
 print 'Usage: sugar-install-bundle [ bundlename ] \n\n\
 Install an activity bundle (.xo). \n'
@@ -16,15 +12,7 @@ if len(sys.argv) != 2:
 cmd_help()
 sys.exit(2)
 
-if 'SUGAR_PROFILE' in os.environ:
-# We are in sugar, so use the bundle registry so the correct signals
-# are sent to the activity list
-from jarabe.model.bundleregistry import get_registry
-registry = get_registry()
-bundle = ActivityBundle(sys.argv[1])
-registry.install(bundle, force_downgrade=True)
-else:
-bundle = ActivityBundle(sys.argv[1])
-bundle.install()
+bundle = ActivityBundle(sys.argv[1])
+bundle.install()
 
 print "%s: '%s' installed." % (sys.argv[0], sys.argv[1])


On Mon, Aug 31, 2015 at 03:53:09PM -0300, Gonzalo Odiard wrote:
> Is a good point.
> Maybe we should add a dbus method to register a bundle,
> and a method in the toolkit to do the call,
> then this script use that method.
> I didn't realized this before, because is included in the sugar module,
> but we should not use jarabe here.
> 
> Gonzalo
> 
> On Mon, Aug 31, 2015 at 2:03 PM, Martin Abente <[1]
> martin.abente.lah...@gmail.com> wrote:
> 
> The problem caused by the race condition is that the activities were not
> refreshed in Sugar activities list when updated or, not added to the list
> when installed. By race condition I mean the situation where the
> BundleRegistry detects changes (e.g. in ~/Activities) too early, when [2]
> activity.info is not available yet, so the bundle gets ignored. I
> personally don't think is related to this issue.
> 
> Now, looking at Tony's report and Sam's confirmation that this issue is
> related to the change in [1], my first guess would be that the problem is
> caused by the overhead generated by initializing the BundleRegistry, and
> any other sugar module imported by it, every time the sugar-install-bundle
> script is executed. Note that the script runs in a different process than
> the sugar shell, so the registry instance returned by get_registry() is 
> not
> the same one as the one in the shell. Having SUGAR_PROFILE set doesn't
> necessarily mean the script is being executed in the same context as the
> shell.
> 
> If my guess is confirmed, we should revise that change or revert it.
> 
> Refs:
> 1. [3]https://github.com/sugarlabs/sugar/commit/
> 64b4b2fba1c37a9ad92ed30eb669b68552b62415
> 
> On Mon, Aug 31, 2015 at 9:02 AM, Gonzalo Odiard <[4]godi...@gmail.com>
> wrote:
> 
> I am wondering if this issue ca be related to the race condition
> detected
> by Martin when the file monitor detect the activity before the [5]
> activity.info file 
> is saved to disk.
> 
> Martin, do you have a patch to test?
> 
> Gonzalo
> 
> On Mon, Aug 31, 2015 at 10:00 AM, Gonzalo Odiard 
> <[6]godi...@gmail.com>
> wrote:
> 
> Tony, 
> If you can enable logging (remove the comment in the line
> SUGAR_LOGGER_LEVEL
> in the file /home/olpc/.sugar/default/debug)
> And install one of the activities without unset the SUGAR_PROFILE
> env variable,
> and send the log, maybe we can understand better what is 
> happening.
> 
> I am afraid the slowness will impact Browse even if you patch it,
> because Browse process
> run in a environment with the env variable set.
> 
> One more question: the time is bigger in slower devices (XO-1) 
> than
> in XO-4,
> or is independent of the hardware performance?
> 
> Gonzalo
> 
> On Sun, Aug 30, 2015 at 7:34 PM, James Cameron 
> <[7]qu...@laptop.org
> > wrote:
> 
> G'day Sam,

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Gonzalo Odiard]

I am wondering if this issue ca be related to the race condition detected
by Martin when the file monitor detect the activity before the activity.info
file
is saved to disk.

Martin, do you have a patch to test?

Gonzalo

On Mon, Aug 31, 2015 at 10:00 AM, Gonzalo Odiard  wrote:

> Tony,
> If you can enable logging (remove the comment in the line
> SUGAR_LOGGER_LEVEL
> in the file /home/olpc/.sugar/default/debug)
> And install one of the activities without unset the SUGAR_PROFILE env
> variable,
> and send the log, maybe we can understand better what is happening.
>
> I am afraid the slowness will impact Browse even if you patch it, because
> Browse process
> run in a environment with the env variable set.
>
> One more question: the time is bigger in slower devices (XO-1) than in
> XO-4,
> or is independent of the hardware performance?
>
> Gonzalo
>
>
> On Sun, Aug 30, 2015 at 7:34 PM, James Cameron  wrote:
>
>> G'day Sam,
>>
>> Adding a flag for a workaround seems like you've given up.  ;-)
>>
>> Wouldn't it be better to fix the problem?  As you can see from
>> #4849 it occurs in Sugar, and only inside Terminal activity.
>>
>> Why is it happening?
>>
>> Why does it take up to 24 minutes to install Browse using Terminal?
>>
>> Why does it take up to 5 minutes to install in Sugar 0.98?
>>
>> And yet only half a second if the bundle registry is bypassed?
>>
>> The bundle registry can't be that slow.
>>
>> By understanding the problem we'll be able to say whether it is
>> causing any other slowness of Sugar.
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> Gonzalo Odiard
>
>


-- 
Gonzalo Odiard
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Gonzalo Odiard]

Tony,
If you can enable logging (remove the comment in the line SUGAR_LOGGER_LEVEL
in the file /home/olpc/.sugar/default/debug)
And install one of the activities without unset the SUGAR_PROFILE env
variable,
and send the log, maybe we can understand better what is happening.

I am afraid the slowness will impact Browse even if you patch it, because
Browse process
run in a environment with the env variable set.

One more question: the time is bigger in slower devices (XO-1) than in XO-4,
or is independent of the hardware performance?

Gonzalo


On Sun, Aug 30, 2015 at 7:34 PM, James Cameron  wrote:

> G'day Sam,
>
> Adding a flag for a workaround seems like you've given up.  ;-)
>
> Wouldn't it be better to fix the problem?  As you can see from
> #4849 it occurs in Sugar, and only inside Terminal activity.
>
> Why is it happening?
>
> Why does it take up to 24 minutes to install Browse using Terminal?
>
> Why does it take up to 5 minutes to install in Sugar 0.98?
>
> And yet only half a second if the bundle registry is bypassed?
>
> The bundle registry can't be that slow.
>
> By understanding the problem we'll be able to say whether it is
> causing any other slowness of Sugar.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
Gonzalo Odiard
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[James Cameron]

G'day Sam,

Adding a flag for a workaround seems like you've given up.  ;-)

Wouldn't it be better to fix the problem?  As you can see from
#4849 it occurs in Sugar, and only inside Terminal activity.

Why is it happening?

Why does it take up to 24 minutes to install Browse using Terminal?

Why does it take up to 5 minutes to install in Sugar 0.98?

And yet only half a second if the bundle registry is bypassed?

The bundle registry can't be that slow.

By understanding the problem we'll be able to say whether it is
causing any other slowness of Sugar.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Tony Anderson]

Hi, Sam P.

The logs are not interesting, only the unzip list of files. The second 
test used time.time() in sugar-install-bundle. It is going through the 
bundle registry. There is

an else option. Perhaps I should try the installs with that branch.

Tony

On 08/29/2015 12:17 PM, Sam P. wrote:

Hi Tony,

Do you have the logs of these installs?  Is there anything in the logs?

Looking back at the commit logs, the change in 0.104 was to use the 
bundle registry to install bundles if sugar is running [1].  Maybe 
that has done something or maybe it is a different change down the line!


Thanks,
Sam

[1] 
https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415


On Sat, Aug 29, 2015 at 8:13 PM Tony Anderson tony_ander...@usa.net 
mailto:tony_ander...@usa.net wrote:


I use sugar-install-bundle to update the configuration of Sugar
activities when preparing laptops at deployments. With 13.2.5, this
script is taking 3-4 times as long
as with previous releases.

I can only speculate on the difference in times since I have 13.2.5 on
all the available XOs and apparently can't flash back.

Specifically,

Browse (some custom modifications)  Test 1: 23 minutes 34 seconds Test
2: 5 minutes 21 seconds
Jukebox (v26 - need gstream 0.1) Test 1: 19 minutes 26 seconds
Test 2: 7
minutes 39 seconds
Quiz  Test 1 6 minutes 52 seconds Test 2 3 minutes 18 seconds

My recollection is that the install on 13.2.1 took less than 10
minutes
overall (including a number of other installs such as codecs, flash,
libre office, gcompris ) with
installation of these three activities taking from 2-3 minutes total.

Tony
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
mailto:Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Tony Anderson]

I use sugar-install-bundle to update the configuration of Sugar 
activities when preparing laptops at deployments. With 13.2.5, this 
script is taking 3-4 times as long

as with previous releases.

I can only speculate on the difference in times since I have 13.2.5 on 
all the available XOs and apparently can't flash back.


Specifically,

Browse (some custom modifications)  Test 1: 23 minutes 34 seconds Test 
2: 5 minutes 21 seconds
Jukebox (v26 - need gstream 0.1) Test 1: 19 minutes 26 seconds Test 2: 7 
minutes 39 seconds

Quiz  Test 1 6 minutes 52 seconds Test 2 3 minutes 18 seconds

My recollection is that the install on 13.2.1 took less than 10 minutes 
overall (including a number of other installs such as codecs, flash, 
libre office, gcompris ) with

installation of these three activities taking from 2-3 minutes total.

Tony
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Sam P.]

Hi Tony,

Do you have the logs of these installs?  Is there anything in the logs?

Looking back at the commit logs, the change in 0.104 was to use the bundle
registry to install bundles if sugar is running [1].  Maybe that has done
something or maybe it is a different change down the line!

Thanks,
Sam

[1]
https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415

On Sat, Aug 29, 2015 at 8:13 PM Tony Anderson tony_ander...@usa.net wrote:

 I use sugar-install-bundle to update the configuration of Sugar
 activities when preparing laptops at deployments. With 13.2.5, this
 script is taking 3-4 times as long
 as with previous releases.

 I can only speculate on the difference in times since I have 13.2.5 on
 all the available XOs and apparently can't flash back.

 Specifically,

 Browse (some custom modifications)  Test 1: 23 minutes 34 seconds Test
 2: 5 minutes 21 seconds
 Jukebox (v26 - need gstream 0.1) Test 1: 19 minutes 26 seconds Test 2: 7
 minutes 39 seconds
 Quiz  Test 1 6 minutes 52 seconds Test 2 3 minutes 18 seconds

 My recollection is that the install on 13.2.1 took less than 10 minutes
 overall (including a number of other installs such as codecs, flash,
 libre office, gcompris ) with
 installation of these three activities taking from 2-3 minutes total.

 Tony
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Tony Anderson]

Hi,

I reran the installs with SUGAR_PROFILE set to False. The install timings:

Browse: 0.5 seconds
Jukebox: 0.5 seconds
Quiz: 0.8 seconds

I'll just patch sugar-install-bundle not to use the SUGAR_PROFILE path.

Thanks for the help.

Tony

On 08/29/2015 01:41 PM, James Cameron wrote:

G'day Sam,

My guess is #4849 again and our user hasn't unset the SUGAR_PROFILE
environment variable as was suggested four months ago.  I never heard
closure on the suggestion, but as it was off-list I'm not surprised.
The ticket shows how to reproduce in case you'd like to take a stab at
it.



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Jerry Vonau]

Hi Tony, 

I brought concerns about that change, with regards to OSbuilder but I guess
that change is slowing down the console now. Have you tried TinyCore[1]
that would boot without setting having SUGAR_PROFILE. I've used TinyCore to
install activities in the past, checkout XO.custom in the source code. Not
sure what effect changing SUGAR_PROFILE might have while sugar is running
but maybe booting to whatever they call runlevel 3(without the gui) might
be an alternative. You'd have to mount the usbkey by hand, but that should
work.  

Hope that helps,

Jerry

1. http://wiki.laptop.org/go/Tiny_Core_Linux

 On August 29, 2015 at 5:43 AM Tony Anderson tony_ander...@usa.net
 wrote:
 
 
 Hi, Sam P.
 
 The logs are not interesting, only the unzip list of files. The second 
 test used time.time() in sugar-install-bundle. It is going through the 
 bundle registry. There is
 an else option. Perhaps I should try the installs with that branch.
 
 Tony
 
 On 08/29/2015 12:17 PM, Sam P. wrote:
  Hi Tony,
 
  Do you have the logs of these installs?  Is there anything in the logs?
 
  Looking back at the commit logs, the change in 0.104 was to use the 
  bundle registry to install bundles if sugar is running [1].  Maybe 
  that has done something or maybe it is a different change down the
  line!
 
  Thanks,
  Sam
 
  [1] 
  https://github.com/sugarlabs/sugar/commit/64b4b2fba1c37a9ad92ed30eb669b68552b62415
 
  On Sat, Aug 29, 2015 at 8:13 PM Tony Anderson tony_ander...@usa.net 
  mailto:tony_ander...@usa.net wrote:
 
  I use sugar-install-bundle to update the configuration of Sugar
  activities when preparing laptops at deployments. With 13.2.5, this
  script is taking 3-4 times as long
  as with previous releases.
 
  I can only speculate on the difference in times since I have 13.2.5
  on
  all the available XOs and apparently can't flash back.
 
  Specifically,
 
  Browse (some custom modifications)  Test 1: 23 minutes 34 seconds
  Test
  2: 5 minutes 21 seconds
  Jukebox (v26 - need gstream 0.1) Test 1: 19 minutes 26 seconds
  Test 2: 7
  minutes 39 seconds
  Quiz  Test 1 6 minutes 52 seconds Test 2 3 minutes 18 seconds
 
  My recollection is that the install on 13.2.1 took less than 10
  minutes
  overall (including a number of other installs such as codecs,
  flash,
  libre office, gcompris ) with
  installation of these three activities taking from 2-3 minutes
  total.
 
  Tony
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  mailto:Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[James Cameron]

G'day Sam,

My guess is #4849 again and our user hasn't unset the SUGAR_PROFILE
environment variable as was suggested four months ago.  I never heard
closure on the suggestion, but as it was off-list I'm not surprised.
The ticket shows how to reproduce in case you'd like to take a stab at
it.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Sam P.]

Hi Tony,

Should we make disabling install via bundle registry (SUGAR_PROFILE) a flag?

There are use cases when it makes sense to install via bundle registry
(updating the activity list) so it is not good to outright disable it.

Thanks,
Sam

On Sat, 29 Aug 2015 11:51 pm Tony Anderson tony_ander...@usa.net wrote:

 Hi,

 I reran the installs with SUGAR_PROFILE set to False. The install timings:

 Browse: 0.5 seconds
 Jukebox: 0.5 seconds
 Quiz: 0.8 seconds

 I'll just patch sugar-install-bundle not to use the SUGAR_PROFILE path.

 Thanks for the help.

 Tony

 On 08/29/2015 01:41 PM, James Cameron wrote:
  G'day Sam,
 
  My guess is #4849 again and our user hasn't unset the SUGAR_PROFILE
  environment variable as was suggested four months ago.  I never heard
  closure on the suggestion, but as it was off-list I'm not surprised.
  The ticket shows how to reproduce in case you'd like to take a stab at
  it.
 

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-install-bundle in 13.2.5 is slooow

[Tony Anderson]

Hi, Sam

The script that installs these activities is run after flashing the 
laptop to provide the capabilities needed for the laptop to work with the
school server. The goal is to have each laptop in the deployment with 
identical software. In this case, the script finishes by a poweroff
command. This means the laptop will be rebooted. At least in all 
previous releases the system registers the activities in the Activities

folder.

However, I am concerned that activities installed from the school server 
will also be affected. If so, it may be fixable with a patch to the
Browse activity. Then it may be necessary for the user to reboot to 
register the activity. (Sad was the day we lost the three-finger salute!).


Obviously, the best solution is to fix the problem. The above are, at 
best, workarounds.


Tony

On 08/29/2015 11:18 PM, Sam P. wrote:


Hi Tony,

Should we make disabling install via bundle registry (SUGAR_PROFILE) a 
flag?


There are use cases when it makes sense to install via bundle registry 
(updating the activity list) so it is not good to outright disable it.


Thanks,
Sam


On Sat, 29 Aug 2015 11:51 pm Tony Anderson tony_ander...@usa.net 
mailto:tony_ander...@usa.net wrote:


Hi,

I reran the installs with SUGAR_PROFILE set to False. The install
timings:

Browse: 0.5 seconds
Jukebox: 0.5 seconds
Quiz: 0.8 seconds

I'll just patch sugar-install-bundle not to use the SUGAR_PROFILE
path.

Thanks for the help.

Tony

On 08/29/2015 01:41 PM, James Cameron wrote:
 G'day Sam,

 My guess is #4849 again and our user hasn't unset the SUGAR_PROFILE
 environment variable as was suggested four months ago.  I never
heard
 closure on the suggestion, but as it was off-list I'm not surprised.
 The ticket shows how to reproduce in case you'd like to take a
stab at
 it.


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
mailto:Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel