/proc/cpuinfo “cache” category: L1, L2 or total

The cache that matters most for directory traversal is the inode cache. This isn't included in the “cache” figure that free displays. It's part of the kernel data (the “slab”). You can see how much memory the various slab pools occupy in /proc/slabinfo (this requires root access). You can use slabtop to see them vary in real time, or this snippet to get a report with each pool's size in bytes:

</proc/slabinfo awk '{print $1, $3*$4}' |sort -k2n

On a typical machine, pressure on the inode cache comes from the nightly updatedb job. If you find how to avoid this, let me know.

The size of the inode cache pool is not fixed, it's determined by a ratio of metadata cache per data cache: the vm.vfs_cache_pressure parameter. You may want to experiment with this — either a low value (the default is 100) to keep more entries in the cache so that the ones from hg aren't displaced, or a high value so that the entries from nightly cron jobs don't stay to pollute RAM.

Finally there's always the hack of running hg status in a morning cron job.

This is the expected output to Arm based processors. All Serialized cores are shown in list with line breaks instead of separated processors. Features are evaluated by cpuinfo code, and only show if all cores support them

         /*
          * Mismatched CPU features are a recipe for disaster. Don't even
          * pretend to support them.
          */
         WARN_TAINT_ONCE(diff, TAINT_CPU_OUT_OF_SPEC,
                         "Unsupported CPU feature variation.");

The other variables are:

• CPU implementer: Your code means ARM;
• CPU architecture: AArch64 means 64 bit ARM board:
• CPU variant : Indicates the variant number of the processor, or "major revision". Yours is zero.
• CPU part: Part number. 0xd03 indicates Cortex-A53 processor.
• CPU revision: Indicates patch release or "minor revision". 3, in your case
• Hardware : HiKey Development Board is self explanatory

If you want to check your processor max clock, just type cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq. To check the current clock dmidecode | grep "Current Speed" should do the trick.

Another thing that could impact the performance of your processor is the cpu governor you are using. Maybe setting the performance one could be better for your needs:

cpupower frequency-set -g performance

Documentation:

• Arm Information
• How to understand the information of my android processor [closed]
• arm64: restore bogomips information in /proc/cpuinfo