Thanks for the additional info.
Termux does provide /sys and /proc, so I can query them w/o root.
My problem is to figure out what they say; I'd just like to know what
the frequency of the cpu running my task is, so that I can estimate
how fast the program should run. For example, I get a very low
'bogomips' number ('38'), but I have no idea what that means,
because I get much higher bogomips numbers from my laptops
(4000 - 5000; even my very old 32bit laptop gets 2500).
Termux on 64bit Android phone:
~ $ cd /sys/devices/system/cpu
../system/cpu $ ls -l
total 0
-r--r--r-- 1 root root 4096 Apr 25 09:05 core_ctl_isolated
drwxr-xr-x 9 root root 0 Jun 22 1970 cpu0
drwxr-xr-x 8 root root 0 Jun 22 1970 cpu1
drwxr-xr-x 8 root root 0 Apr 25 06:03 cpu2
drwxr-xr-x 8 root root 0 Apr 25 06:03 cpu3
drwxr-xr-x 8 root root 0 Apr 25 05:42 cpu4
drwxr-xr-x 8 root root 0 Apr 25 05:41 cpu5
drwxr-xr-x 8 root root 0 Apr 24 09:07 cpu6
drwxr-xr-x 8 root root 0 Apr 25 05:41 cpu7
drwxr-xr-x 5 root root 0 Apr 24 09:07 cpufreq
drwxr-xr-x 2 root root 0 Apr 25 09:05 cpuidle
drwxr-xr-x 2 root root 0 Apr 25 09:05 gladiator_hang_detect
drwxr-xr-x 2 root root 0 Apr 25 09:05 hang_detect_gold
drwxr-xr-x 2 root root 0 Apr 25 09:05 hang_detect_silver
drwxr-xr-x 2 root root 0 Apr 25 09:05 hotplug
-r--r--r-- 1 root root 4096 Apr 25 09:05 isolated
-r--r--r-- 1 root root 4096 Apr 25 09:05 kernel_max
-r--r--r-- 1 root root 4096 Apr 25 09:05 modalias
-r--r--r-- 1 root root 4096 Apr 25 09:05 offline
-r--r--r-- 1 root root 4096 Apr 25 06:08 online
-r--r--r-- 1 root root 4096 Apr 25 09:05 possible
drwxr-xr-x 2 root root 0 Apr 25 09:05 power
-r--r--r-- 1 root root 4096 Apr 25 08:49 present
-rw-r--r-- 1 root root 4096 Apr 25 09:05 uevent
drwxr-xr-x 2 root root 0 Apr 25 09:05 vulnerabilities
../system/cpu $ cd cpufreq
../cpu/cpufreq $ ls -l
total 0
drwxr-xr-x 4 root root 0 Apr 24 09:07 policy0
drwxr-xr-x 4 root root 0 Apr 24 09:07 policy6
drwxr-xr-x 4 root root 0 Apr 24 09:07 policy7
../cpu/cpufreq $
-----Original Message-----
From: <picolisp@software-lab.de>
Sent: Apr 25, 2023 7:09 AM
To: <picolisp@software-lab.de>
Subject: Re: Turn up the CPU clocks under Android Termux ??
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 :
> 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:
> Sent: Apr 24, 2023 12:21 PM
> To:
> 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
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
