Start-up progress appearing late #297

Closed
rscottm opened this Issue Nov 25, 2012 · 7 comments

Comments

Projects
None yet
2 participants
Owner

rscottm commented Nov 25, 2012

I've noticed that the start-up progress spinner seems to come up late and the screen will be mostly blank until it appears. I've followed the code and my best guess is that this is due to the heap allocation. It seems that heap allocation might block other threads (or at least keep other threads from progressing quickly). I experimented with workarounds and have had some success with adding a short delay (200ms) before the heap allocation (just yielding did not work). I'm not sure this is the best solution. Anyone else seeing this problem?

Owner

donv commented Nov 25, 2012

I am seeing the same problem. What happens if you remove the allocation altogether? The allocation has a positive effect on larger apps, but should maybe not be present on small apps. I have an issue for this: #176

I am thinking we can release without a fix for this, but it would be better if the start-up progress would appear quickly.

It would be good to have some actual numbers on this. Maybe measure it with the Ruboto Benchmarks app?

Owner

donv commented Nov 28, 2012

Any progress on this one?

Owner

donv commented Dec 1, 2012

@rscottm Do you think you will have time to look at this this weekend? I'd like to release Ruboto 0.10.0 today or tomorrow.

Owner

donv commented Dec 1, 2012

I measured the time for the actual memory alloc, and got 30-69ms on a few runs.

Suddenly I cannot reproduce the problem...do you still have it @rscottm ?

Owner

rscottm commented Dec 1, 2012

I haven't had time to focus on it. I'm still slogging through Ruboto IRB
demo scripts. I don't think it's a huge issue to either release with it as
it is or release with out the memory alloc for now.

There could be other issues involved. Let's leave this open and do some
more experimentation before 1.0.

On Sat, Dec 1, 2012 at 3:00 AM, Uwe Kubosch notifications@github.comwrote:

I measured the time for the actual memory alloc, and got 30-69ms on a few
runs.

Suddenly I cannot reproduce the problem...do you still have it @rscottmhttps://github.com/rscottm?


Reply to this email directly or view it on GitHubhttps://github.com/ruboto/ruboto/issues/297#issuecomment-10915924.

donv was assigned Dec 1, 2012

Owner

donv commented Dec 1, 2012

I'll remove the memory alloc, and move to this issue to 0.10.1.

Owner

donv commented Dec 30, 2012

I am not seeing this anymore, so I'll close it.

donv closed this Dec 30, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment