On Wed, Mar 13, 2013 at 12:28 PM, Matthew Toseland <toad at amphibian.dyndns.org> wrote: > On Tuesday 12 Mar 2013 19:23:51 Kasper wrote:
>> >> Only real problem I have now is that libjcpuid apparently only exists >> for x86 and I can't find the sources to try and compile it for ARM >> myself (if even possible). I do not know if that's the reason it uses >> too much CPU - between 90-100% at all times. > > Does it manage to load the native version of libjbigi? IMHO the native thread > library is probably most important in terms of interactive usability. Yes. It manages to load both the native version libjbigi and libNativeThread, and I could really feel a difference in responsiveness from compiling these as native, so I'd say you are right they are most important for interactive usability. >> But I managed to get it working on this alternative architecture, >> despite being rather new to both Linux and ARM, although with basic >> understanding of programming and compiling. It would not take much to >> make such support out of the box, as seen by my experiences, although >> of course optimizing could be another matter. But I guess getting >> freenet-ext.jar carved up in smaller parts would be a big help both >> for tweaking, and official support. But I definitely see an advantage >> in being available for ARM devices for a program that should ideally >> run 24/7. If I could get lower CPU usage it would run 24/7 at my place >> now. Any advise on configurations to tweak to try and lower it or >> insights regarding whether I'm correct in suspecting the lack of >> libjcpuid is why it's running full throttle all the time? > > Yes, we should support it out of the box. Well I hope I can help even if just a little. If nothing else by confirming how close you are... I really lack both the theoretical foundation and programming skills to contribute much directly, but I'd be happy to do what I can, which at this point is probably mostly testing, and feedback unfortunately...
