HP Forum Archive 15

[ Return to Index | Top of Index ]

48GX computing delay Message #1 Posted by Steve Jirsa on 30 Nov 2005, 6:58 p.m. I have a 48GX which often has a several second delay when performing basic arithmetic. Has anyone else experienced this and is there anything that can be done?

Re: 48GX computing delay Message #2 Posted by Han on 30 Nov 2005, 11:00 p.m., in response to message #1 by Steve Jirsa I have a 48GX (several actually), a 48G (again several) and 48G+ (just one). I also have several 48SX models. I would be willing to test out your calculations on these models and time them for you for comparison. Could you give us some details as to what it is you are calculating? Han

Re: 48GX computing delay Message #3 Posted by steve jirsa on 1 Dec 2005, 11:43 a.m., in response to message #2 by Han It's usually just basic multiplication or division and it seems to happen pretty randomly.

Re: 48GX computing delay Message #4 Posted by Arnaud Amiel on 1 Dec 2005, 12:06 p.m., in response to message #3 by steve jirsa Wouldn't it be garbage collection? It would especially happen if you don't have much in memory. Arnaud

Re: 48GX computing delay Message #5 Posted by Han on 1 Dec 2005, 4:59 p.m., in response to message #4 by Arnaud Amiel I believe you are correct. During garbage collection, the calculator will be seemingly slower. The goal of garbage collection is to get rid of temporary objects in memory which are no longer referenced. If you are low on memory, then the HP 48 will try to garbage collect often in an attempt to get more working memory. Is this the case? Do you have very little free memory?

Re: 48GX computing delay Message #6 Posted by Arnaud Amiel on 2 Dec 2005, 4:51 a.m., in response to message #5 by Han If you have little memory, the garbage collection will be quite fast as it does not need to tidy much. However, if you have lots of free memory, it will not happen so often but will take much longer. Basically, it works like this, the hp leaves all its temporary calculation, objects, rubbish in memory until it feels the memory is too full. It then cleans everything and starts again. If less space (memory) is available, it will have to clean more often but will have less work to do each time and you would not notice it. When the 49 was introduced with 256 K of free RAM there was lots of people complaining about the garbage collection delay. The solution was to store a huge string in memory to have only say 64K left and adjust the size of this string to your memory requirements. Garbage collection was later improved to cope with the 256K. Arnaud

Re: 48GX computing delay Message #7 Posted by Han on 2 Dec 2005, 4:27 p.m., in response to message #6 by Arnaud Amiel Ahh... I truly blundered then. I had assumed that with such little memory, gargabe collection would occur so often that the frequency of gargabe collection was what was noticable. It makes more sense the way you described it. Just out of curiosity: how did they make the fix for the 256kB of memory? Edited: 2 Dec 2005, 4:27 p.m.

Re: 48GX computing delay Message #8 Posted by Arnaud Amiel on 2 Dec 2005, 5:45 p.m., in response to message #7 by Han I believe that the Garbage collector of the 49G was rewritten completely in a ROM update. It still happens but it is much fatser. On the 49g+ I believe it was directly implemented in ARM Arnaud

[ Return to Index | Top of Index ]

Go back to the main exhibit hall