|
2015-09-08
, 23:48
|
Posts: 338 |
Thanked: 496 times |
Joined on Oct 2010
|
#122
|
|
2015-09-09
, 02:51
|
Posts: 193 |
Thanked: 348 times |
Joined on Dec 2009
|
#123
|
|
2015-09-09
, 03:32
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#124
|
An excellent suggestion.
One last question: how exactly do you suggest to achieve that on my Jolla?
(Actually, my main PC up to September 2013 had 1GB RAM and no swap and it never ran out of memory, despite habitually running some quite heavy applications. Just the antivirus alone took about 30%. That a mobile phone with the same amount of RAM cannot manage even three running apps is a scandal that screams "incompetence" loudly and clearly for the whole world to hear.)
|
2015-09-09
, 06:05
|
Posts: 121 |
Thanked: 231 times |
Joined on Oct 2013
|
#125
|
A lot of people in this thread are acting like big OOM & resource issues and the handling of them, poor performance and unreliability are something new to them or new to this update. i can only assume they've either not used sailfish much or at all prior to (pre)2.0 or were hoping that it would be some kind of magic bullet ... or was the already chronic situation really made that much worse? i've yet to try it as i'm away and 'hacking' the update is the last thing i want to do. but for those who have tried it and already took a dim view of the status quo, what's the state of play with 1.1.9 ... could it really be worse in those respects, or were people just being very naive about what 2.0 might bring. Tbh I'm done with Sailfish if resource handling gets worse ... it's almost intolerable as it is.
The Following User Says Thank You to TemeV For This Useful Post: | ||
|
2015-09-09
, 07:30
|
|
Posts: 1,196 |
Thanked: 2,708 times |
Joined on Jan 2010
@ Hanoi
|
#126
|
Forget about swap on flash media, whether it be on raw disk partition or on top of filesystem...
Swap on flash is a BAD IDEA and it WILL kill your flash.
|
2015-09-09
, 07:39
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#127
|
A lot of people in this thread are acting like big OOM & resource issues and the handling of them, poor performance and unreliability are something new to them or new to this update. i can only assume they've either not used sailfish much or at all prior to (pre)2.0 or were hoping that it would be some kind of magic bullet ...
|
2015-09-09
, 08:23
|
Posts: 338 |
Thanked: 496 times |
Joined on Oct 2010
|
#128
|
The Following User Says Thank You to bluefoot For This Useful Post: | ||
|
2015-09-09
, 08:52
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#129
|
Big chunk of that RAM is taken by the Android support. Killing it gives you 50% free, which is okay for a number of concurrent tasks.
As for the 1GB RAM PC - do you run a browser in it? It will swallow your RAM in one go, especially Chrome
--- | SailfishOS 1.1.7.28 (Björnträsket) (armv7hl) '--- [nemo@Dinghy ~]$ free total used free shared buffers cached Mem: 825664 725376 100288 0 6516 200052 -/+ buffers/cache: 518808 306856 Swap: 627516 102652 524864 [nemo@Dinghy ~]$ free total used free shared buffers cached Mem: 825664 570696 254968 0 6516 200416 -/+ buffers/cache: 363764 461900 Swap: 627516 102652 524864 [nemo@Dinghy ~]$
The Following 9 Users Say Thank You to pichlo For This Useful Post: | ||
|
2015-09-09
, 10:30
|
|
Posts: 1,196 |
Thanked: 2,708 times |
Joined on Jan 2010
@ Hanoi
|
#130
|
That commonly repeated excuse may apply in most people's cases but not in mine. My Jolla has never been tarnished with Android and will never be, if I can help it.
Chrome is a Google product and as such I would never touch it with a barge pole but yes, of course I regularly used a browser - Firefox in my case - with more than three tabs open without FF ever having to reload any of them when I switched between them. I am not a big fan of keeping hundreds of tabs but if a browser cannot keep 5-6 open at the same time then something is terribly wrong.
Look, instead of speculations, how about some hard numbers.
Here are two 'free' reports.
In both cases, Terminal and some background processes were running, including the Meecast, Call Recorder and SysMon daemons. In the first case, Browser was running as well with one tab open showing this thread. That may account for the 150 MB difference but how on earth do you account for the 570 MB base?Code:--- | SailfishOS 1.1.7.28 (Björnträsket) (armv7hl) '--- [nemo@Dinghy ~]$ free total used free shared buffers cached Mem: 825664 725376 100288 0 6516 200052 -/+ buffers/cache: 518808 306856 Swap: 627516 102652 524864 [nemo@Dinghy ~]$ free total used free shared buffers cached Mem: 825664 570696 254968 0 6516 200416 -/+ buffers/cache: 363764 461900 Swap: 627516 102652 524864 [nemo@Dinghy ~]$
Just think about it. The bare OS plus a couple of measly daemons consume 570 out of 825 MB RAM! That's 69%. For just the OS! With no applications running. On my PC, the bare OS, when I disabled the anti-virus, took less than 140 MB, or about 14%.
And this is supposed to be on a mobile device, one that the developers knew it was going to run with limited resources. My PC was a 9 years old laptop, running a modern, unoptimised OS designed for quadcore machines with 8 times as much memory as I was able to provide. How is this even possible?
The Following 3 Users Say Thank You to ste-phan For This Useful Post: | ||
One last question: how exactly do you suggest to achieve that on my Jolla?
(Actually, my main PC up to September 2013 had 1GB RAM and no swap and it never ran out of memory, despite habitually running some quite heavy applications. Just the antivirus alone took about 30%. That a mobile phone with the same amount of RAM cannot manage even three running apps is a scandal that screams "incompetence" loudly and clearly for the whole world to hear.)