[Gen9 Android Development] momojuro:
As promised, here are the changes that I found which gave me a good performance and multitasking improvements, and I will explain my choices too. Some feedbacks and/or a little thankie will be really appreciated !

512MB boards

- Firstly, you need to mount RW your tablet. For so, type both of these lines one by one via ADB or via Terminal :

su
mount -o remount, rw /

- Secondly, we will begin first with the build.prop flags changes. Our tablet needs the right Dalvik VM values which follow its physical memory resources. Also, those settings were also tuned to avoid memory pressure with multiple cached app processes while switching between applications. In addition, I changed the ART runtime parameters (thanks [MENTION=4258165]SebyD[/MENTION] ) to limit greatly the freezes.

Now, you will need to put my following lines instead of the ones present in the build.prop (/system/build.prop) file using CM File Manager (sentences written with a bold text is to help you for so, don't add them) :

dalvik.vm.heapstartsize=5m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapgrowthlimit=48m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapsize=96m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heaptargetutilization=0.9 [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapminfree=512k [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapmaxfree=2m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.dex2oat-flags=--no-watch-dog [b]- Add this one.[/b]
dalvik.vm.dex2oat-filter=verify-none [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.image-dex2oat-filter=balanced [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.dex2oat-Xmx=96m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.image-dex2oat-Xmx=96m [b]- This line already exists, simply change its value with mine.[/b]

- Thirdly and without rebooting the tablet yet, we will change some kernel memory settings. These settings will allocate about 26% the physical memory that is generally available for user processes to a compressed swap area (ZRAM) and instruct the kernel to aggressively use swap for dirty pages (so clean pages tend to stay in the page cache). The big positive trade-off is that it will be possible to run programs of much larger size than the physical memory generally available for user applications. Also, by default, the Linux kernel swaps in 8 pages of memory at a time. But when using ZRAM, the incremental cost of reading 1 page at a time is negligible and may help in case the device is under extreme memory pressure, and I decided to implent that too. In addition again, I increased the read_ahead_kb value basing on the Nexus 7 (2013) init.rc file to gives a better read and/or write speeds.

For so, you will need to find the lines below and to change its by default values by the ones that I proposed in the init.archos_init.rc file (you can find it in the root (/) directory of the device) :

write /proc/sys/vm/page-cluster 0
write /proc/sys/vm/swappiness 100

And you will need to add these just after the Memory management parameters part :

# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 1024

- Finally, there are still two things to do :

a) I updated again my performance shell script file with new ROW scheduler values which supplement the default kernel's ones and give a better overall performance. I also updated the debugging disable part (thanks [MENTION=5514152]Paget96[/MENTION] ). From your side, you will need to put my joined script in the /system/etc/init.d directory and to give the right needed permissions using this command via ADB or Terminal :

chmod 775 /system/etc/init.d/99Performance

b) And to finish, we will wipe the dalvik-cache using CM File Manager by removing the content of the dalvik-cache (/data/dalvik-cache) folder. Now you can reboot !

1GB boards

- Firstly, you need to mount RW your tablet. For so, type both of these lines one by one via ADB or via Terminal :

su
mount -o remount, rw /

- Secondly, we will begin first with the build.prop flags changes. Our tablet needs the right Dalvik VM values which follow its physical memory resources. Also, those settings were also tuned to avoid memory pressure with multiple cached app processes while switching between applications. In addition, I changed the ART runtime parameters (thanks [MENTION=4258165]SebyD[/MENTION] ) to limit greatly the freezes.

Now, you will need to put my following lines instead of the ones present in the build.prop (/system/build.prop) file using CM File Manager (sentences written with a bold text is to help you for so, don't add them) :

dalvik.vm.heapstartsize=8m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapgrowthlimit=100m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapsize=174m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.heapminfree=512k [b]- This line already exists, simply change its value with mine (if it's not the same, I didn't remember).[/b]
dalvik.vm.heapmaxfree=8m [b]- This line already exists, simply change its value with mine (if it's not the same, I didn't remember).[/b]
dalvik.vm.dex2oat-flags=--no-watch-dog [b]- Add this one.[/b]
dalvik.vm.dex2oat-filter=verify-none [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.image-dex2oat-filter=balanced [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.dex2oat-Xmx=174m [b]- This line already exists, simply change its value with mine.[/b]
dalvik.vm.image-dex2oat-Xmx=174m [b]- This line already exists, simply change its value with mine.[/b]

- Thirdly and without rebooting the tablet yet, we will change some kernel memory settings. These settings will allocate about 26% the physical memory that is generally available for user processes to a compressed swap area (ZRAM) and instruct the kernel to aggressively use swap for dirty pages (so clean pages tend to stay in the page cache). The big positive trade-off is that it will be possible to run programs of much larger size than the physical memory generally available for user applications. Also, by default, the Linux kernel swaps in 8 pages of memory at a time. But when using ZRAM, the incremental cost of reading 1 page at a time is negligible and may help in case the device is under extreme memory pressure, and I decided to implent that too. In addition again, I increased the read_ahead_kb value basing on the Nexus 7 (2013) init.rc file to gives a better read and/or write speeds.

For so, you will need to find the lines below and to change its by default values by the ones that I proposed in the init.archos_init.rc file (you can find it in the root (/) directory of the device) :

write /proc/sys/vm/page-cluster 0
write /proc/sys/vm/swappiness 100

And you will need to add these just after the Memory management parameters part :

# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 2048

- Finally, there are still three things to do :

a) I updated again my performance shell script file with new ROW scheduler values which supplement the default kernel's ones and give a better overall performance. I also updated the debugging disable part (thanks [MENTION=5514152]Paget96[/MENTION] ). From your side, you will need to put my joined script in the /system/etc/init.d directory and to give the right file permissions using this command via ADB or Terminal :

chmod 755 /system/etc/init.d/99Performance

b) We will increase the ZRAM disk size to 256MB (which is 26% as I said before of the total phyisical memory), as the default one isn't enough for multitasking simultaneously memory hungry apps. For so, you will need to change this line of your model's (101/80H or 101/80S) fstab file to this one :

/dev/block/zram0	none swap	defaults	zramsize=268435456

c) And to finish, we will wipe the dalvik-cache using CM File Manager by removing the content of the dalvik-cache (/data/dalvik-cache) folder. Now you can reboot !

Sources :

01.org - Android Memory Tuning for Android 5.0/5.1.

Franco's Dev Team - Various tunables and tweaks.

The Android Source Code - Configuring ART.

The Android Source Code - Low RAM Configuration.