[expo-file-system] `FileSystem.readAsStringAsync` gets increasingly slower when called in a loop about expo HOT 2 CLOSED

Just as another test, I took the obvious performance improvement and ran all the functions in parallel with Promise.allSettled and they still have an increasing time.

Code is available in the same reproduction https://github.com/AlexanderHott/slow-expo-file-system

 LOG  data [36.656453013420105, 37.94299300014973, 39.215048000216484, 40.38867200911045, 41.60709600150585, 42.62133799493313, 43.65311600267887, 45.618001997470856, 47.21626798808575, 48.447062000632286, 53.82718899846077, 54.94844500720501, 56.557698011398315]

from expo.

I overlooked a small detail on my end. The call to const start = performance.now() is run immediately, while the await directly after it may not start executing it immediately, essentially making it cumulative.

However, when debugging this issue, I found that readAsStringAsync spends almost half it's executing time serializing the bytes as base64, and I spend a greater amount of time decoding it on the javascript side. Would there be a way to avoid this overhead?

from expo.