http://www.reactnativeexpress.com
اگه دوست دارید ری اکت نیتیو یاد بگیرید این داکیومنت خوب و کاملی هستش
آخرشم چندتا اپ میزنید که یکیش یه قمست از اپ Uber هستش
اگه دوست دارید ری اکت نیتیو یاد بگیرید این داکیومنت خوب و کاملی هستش
آخرشم چندتا اپ میزنید که یکیش یه قمست از اپ Uber هستش
Forwarded from The Art of Programming (tan)
Something you might not know - from Python 3.6 onwards, dictionary keys stay in the order they were inserted:
https://stackoverflow.com/questions/39980323/are-dictionaries-ordered-in-python-3-6
https://stackoverflow.com/questions/39980323/are-dictionaries-ordered-in-python-3-6
Stack Overflow
Are dictionaries ordered in Python 3.6+?
Dictionaries are insertion ordered as of Python 3.6. It is described as a CPython implementation detail rather than a language feature. The documentation states:
dict() now uses a “compact”
dict() now uses a “compact”
Learning-React-Native.pdf
15.5 MB
کتاب آموزش ری اکت نیتیو
از مجموعه انتشارات OREILLY
از مجموعه انتشارات OREILLY
Forwarded from Dataacademy.ir
چه مفاهیمی را نمی توان داده کاوی نامید! چه چیزهایی داده کاوی نیست!!! https://goo.gl/QoFJcA
Forwarded from Tech C**P (Alireza Hos.)
Make your
Django deliberately doesn’t serve media for you, and it’s designed that way to save you from yourself. If you try to serve media from the same Apache instance that’s serving Django, you’re going to absolutely kill performance. Apache reuses processes between each request, so once a process caches all the code and libraries for Django, those stick around in memory. If you aren’t using that process to service a Django request, all the memory overhead is wasted.
So, set up all your media to be served by a different web server entirely. Ideally, this is a physically separate machine running a high- performance web server like lighttpd or tux. If you can’t afford the separate machine, at least have the media server be a separate process on the same machine.
For more information on how to separate static folder:
- https://docs.djangoproject.com/en/dev/howto/static-files/#howto-static-files
If you can afford it, stick your database server on a separate machine, too. All too often Apache and PostgreSQL (or MySQL or whatever) compete for system resources in a bad way. A separate DB server — ideally one with lots of RAM and fast (10k or better) drives — will seriously improve the number of hits you can dish out.
I don’t totally understand how KeepAlive works, but turning it off on our Django servers increased performance by something like 50%. Of course, don’t do this if the same server is also serving media… but you’re not doing that, right?
Although Django has support for a number of cache backends, none of them perform even half as well as memcached does. If you find yourself needing the cache, do yourself a favor and don’t even play around with the other backends; go straight for memcached.
#python #django #memcached
Django application blazing fast by doing some tips:1- Use a separate media server:Django deliberately doesn’t serve media for you, and it’s designed that way to save you from yourself. If you try to serve media from the same Apache instance that’s serving Django, you’re going to absolutely kill performance. Apache reuses processes between each request, so once a process caches all the code and libraries for Django, those stick around in memory. If you aren’t using that process to service a Django request, all the memory overhead is wasted.
So, set up all your media to be served by a different web server entirely. Ideally, this is a physically separate machine running a high- performance web server like lighttpd or tux. If you can’t afford the separate machine, at least have the media server be a separate process on the same machine.
For more information on how to separate static folder:
- https://docs.djangoproject.com/en/dev/howto/static-files/#howto-static-files
2- Use a separate database server:If you can afford it, stick your database server on a separate machine, too. All too often Apache and PostgreSQL (or MySQL or whatever) compete for system resources in a bad way. A separate DB server — ideally one with lots of RAM and fast (10k or better) drives — will seriously improve the number of hits you can dish out.
3- Turn off KeepAlive:I don’t totally understand how KeepAlive works, but turning it off on our Django servers increased performance by something like 50%. Of course, don’t do this if the same server is also serving media… but you’re not doing that, right?
4- Use memcached:Although Django has support for a number of cache backends, none of them perform even half as well as memcached does. If you find yourself needing the cache, do yourself a favor and don’t even play around with the other backends; go straight for memcached.
#python #django #memcached
Tech C**P
Make your Django application blazing fast by doing some tips: 1- Use a separate media server: Django deliberately doesn’t serve media for you, and it’s designed that way to save you from yourself. If you try to serve media from the same Apache instance…
Somehow BS
1-Use nginx
Use uwsgi
3- that’s because you are using modpython
Use uwsgi
4-cache backend has a little effect compared to cache method
Redis works pretty good
1-Use nginx
Use uwsgi
3- that’s because you are using modpython
Use uwsgi
4-cache backend has a little effect compared to cache method
Redis works pretty good
LinkPlace
https://roocket.ir/series/electron-tutorial/episode/28
آقا جدا از این کارا میخواین بکنین با الکترون نکنین