There are three separate issues here: - making sure Termux doesn't sleep (wake lock does that) - controlling on what core type the process runs ( see taskset ) - controlling the frequency of that core (via CPU governor)
The latter certainly requires root. The middle i have not experimented with. It is highly likely that the scheduler heavily pushes long running programs onto the efficiency cores as phones optimise for battery life not throughput. It might even ignore simple corr affinity stuff but that i don't know. I hope that helps. 24.04.2023 22:20:32 Henry Baker <picolisp@software-lab.de>: > Thanks; I didn't understand your original suggestion that > 'termux-wake-lock' was an actual termux command. > > Sadly, 'termux-wake-lock' didn't help speed things up, either. > > So either I've vastly overestimated the speed of my cellphone, > or there's some other software problem (e.g., something > getting interpreted instead of getting compiled... ???). Or > perhaps my cellphone is thermally limited -- it simply may > not have the ability to dissipate the heat from running any > faster, so it gets throttled to avoid overheating. > > I appreciate your excellent suggestions! > > -----Original Message----- > From: <picolisp@software-lab.de> > Sent: Apr 24, 2023 12:21 PM > To: <picolisp@software-lab.de> > Subject: Re: Turn up the CPU clocks under Android Termux ?? > > On Mon, Apr 24, 2023 at 07:01:39PM +0000, Henry Baker wrote: >> So either my program really is running at full speed (which I highly doubt), >> or Termux itself needs to be fixed to enable full speed. > > I don’t think you have to fix anything. Have you actually tried > taking the lock? This can be done through a button in the > notification. See also: https://wiki.termux.com/wiki/Termux-wake-lock > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
