Re: cairo has now 16bit surfaces (was Fwd: rendering-cleanup)

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 02:20, Bernie Innocenti ber...@codewiz.org wrote: El Tue, 03-08-2010 a las 16:26 +0200, Tomeu Vizoso escribió: This means that graphic operations would be considerably faster on the XO-1 because to date we are rendering to 24bit surfaces that the X server has to convert

Re: MicroSD Card performance variance on XO-1.5

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 02:52, Bernie Innocenti ber...@codewiz.org wrote: El Fri, 06-08-2010 a las 18:50 +0200, Tomeu Vizoso escribió: I also think our vm.dirty_* settings are wrong and likely causing our current fill-buffer-and-stutter behaviour. We are using the defaults and those are for

Re: MicroSD Card performance variance on XO-1.5

2010-08-07 Thread Bernie Innocenti
[cc += sugar-devel, tch] El Sat, 07-08-2010 a las 11:27 +0200, Tomeu Vizoso escribió: Btw, have read that some notifications about available memory have landed in cgroups in recent kernels. The Sugar shell could listen to those and give a chance to background activities to save their state

Re: cairo has now 16bit surfaces (was Fwd: rendering-cleanup)

2010-08-07 Thread Bernie Innocenti
El Sat, 07-08-2010 a las 11:25 +0200, Tomeu Vizoso escribió: I'd expect well-written code to call cairo_surface_create_similar() whenever possible, but there might be hot-spots in our software stack that assume 32bpp. Have given a look to gtk+ and the xlib backend of cairo and seems to

Re: MicroSD Card performance variance on XO-1.5

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 18:11, Bernie Innocenti ber...@codewiz.org wrote: [cc += sugar-devel, tch] El Sat, 07-08-2010 a las 11:27 +0200, Tomeu Vizoso escribió: Btw, have read that some notifications about available memory have landed in cgroups in recent kernels. The Sugar shell could listen

Re: cairo has now 16bit surfaces (was Fwd: rendering-cleanup)

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 18:14, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 07-08-2010 a las 11:25 +0200, Tomeu Vizoso escribió: I'd expect well-written code to call cairo_surface_create_similar() whenever possible, but there might be hot-spots in our software stack that assume 32bpp.

Killing activities when memory gets short

2010-08-07 Thread Bernie Innocenti
El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió: So we would have a periodic wakeup? The test would be the amount of free memory plus buffers and caches? A polled design is clearly inferior to a proper notification system, but it has the advantage of being simple and not requiring

Re: Killing activities when memory gets short

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 19:31, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió: So we would have a periodic wakeup? The test would be the amount of free memory plus buffers and caches? A polled design is clearly inferior to a proper

Re: cairo has now 16bit surfaces (was Fwd: rendering-cleanup)

2010-08-07 Thread Bernie Innocenti
El Sat, 07-08-2010 a las 18:19 +0200, Tomeu Vizoso escribió: Sounds good, if that gives problems we can consider backporting just that patch. If the small patch below is really what was needed, I'm going to feel quite stupid:

Re: Killing activities when memory gets short

2010-08-07 Thread Tomeu Vizoso
On Sat, Aug 7, 2010 at 19:33, Tomeu Vizoso to...@sugarlabs.org wrote: On Sat, Aug 7, 2010 at 19:31, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió: So we would have a periodic wakeup? The test would be the amount of free memory plus

Re: Killing activities when memory gets short

2010-08-07 Thread Bernie Innocenti
El Sat, 07-08-2010 a las 19:33 +0200, Tomeu Vizoso escribió: BTW, looking at top, it seems that Sugar and other processes wake up quite frequently when the system is supposed to be completely idle. It may be background checks for updates, NetworkManager updates or the presence service.

Lazy Network Neighborhood updates

2010-08-07 Thread Bernie Innocenti
El Sat, 07-08-2010 a las 19:36 +0200, Tomeu Vizoso escribió: On a second thought, Sugar should probably only listen to events relevants to what is being currently displayed. This would display outdated data for a short while and would mean significant rework but may be a worthy goal for the

Re: Killing activities when memory gets short

2010-08-07 Thread Tiago Marques
Hi all, On Sat, Aug 7, 2010 at 6:31 PM, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió: So we would have a periodic wakeup? The test would be the amount of free memory plus buffers and caches? A polled design is clearly inferior to

Re: [Sugar-devel] Lazy Network Neighborhood updates

2010-08-07 Thread Gary Martin
Hi Mikus, On 7 Aug 2010, at 20:01, Mikus Grinbergs mi...@bga.com wrote: We already readjust the network neighborhood layout on the fly when we switch view. It's funny to see the access points slide around :-) Haven't bothered to keep track of the appearance/disappearance of XO and AP

Re: [Sugar-devel] Lazy Network Neighborhood updates

2010-08-07 Thread Mikus Grinbergs
invitation icons seem to persist long after all invitors/invitees are gone. is this as 'simple' as removing the notification when the activity id is no longer being shared? Or would you like the UI to still indicate that you had missed the event/s? I imagine if someone clicks on an

Re: Killing activities when memory gets short

2010-08-07 Thread Martin Langhoff
On Sat, Aug 7, 2010 at 1:31 PM, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió: So we would have a periodic wakeup? The test would be the amount of free memory plus buffers and caches? A polled design is clearly inferior to a proper

[Server-devel] Exporting Moodle config from XS

2010-08-07 Thread David Leeming
Is it possible to export the Moodle configuration from the XS and then install it on another server intended for another site? Obviously the user data is not important in this instance. However the second example would be backing it up, when user data is important. David Leeming