

- #Dont see ultracopier on linux android#
- #Dont see ultracopier on linux software#
- #Dont see ultracopier on linux code#
#Dont see ultracopier on linux android#
We don’t have control on big company then forgot support the last android on 5 years phone. In this context: Every body try hard to just save few % of resources for the earth.

It’s fully functional, very good for the assigned task. I have lot of running hardware in 32Bits.
#Dont see ultracopier on linux code#
For 32Bits, in C/C++, some dirty code cast pointer to integer, that’s generate problem on 32/64 barrier, added to less popular each years then less maintained by the owner of each project, …Ħ4Bits support is too hard than do generic support with clean code.Ībout obsolescence, the ARM quit 32Bits into the last 10 years.
#Dont see ultracopier on linux software#
But lot of software in the system are in C/C++, with old code, that’s mean: Each time where you have system specific or architecture specific code, you need adapt to new system/architecture. When you have code abstraction (as Python, Java, C#), porting is transparent then easy to support another architecture.

What is the problem with other Architecture for Linux and developer? (And maybe do my own http server) Publié le 16 juillet 2020 16 juillet 2020 Catégories Architecture et conception logicielle, Confiared, Internet, Uncategorized Mots-clés CDN, FastCGI, io_uring, nginx Architecture 32Bits, drop the support The future improvement are: better cache, cache some stuff where needed (DNS, …), use io_uring to improve file access and be 3x more fast than Nginx with static file, do profile to optimize the code. An internal page is served 3x more faster than a simple « Hello world » into PHP 7.4. That’s greatly improve the performance, reduce the memory. I parse the protocols (DNS, FastCGI, …) on fly. The code is specific, not flexible and generalist. I choose monothread to have great performance without thread coherency code (more simple to dev, more eficience if the code is very fast because if the code is very fast most of the time is consumed into thread management and data migration from a CPU to another CPU). If same url is already downloading, then the content is send from the partial downloaded content. Then I have rewritten the CDN as standalone FastCGI server, the cache is directly controlled by the server. This solution lack fine cache control tuning, some bug due to Nginx cache. We was with Nginx + Nginx FastCGI cache + PHP (to just proxy the reply). Hi, to improve the service into Confiared I’m rewritting the CDN software.
