Re: [uWSGI] Help

2019-03-04 Thread Tamer Higazi
okay, I didn't see the AWS term. had tomatos on my eyes. Sorry. You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM. Main problem!? Really!? He's on AWS of couse it's 64bits, 2 CPU cores is a LOT of power for more than 20 users, I serve 50 concurent user on AWS with a

Re: [uWSGI] Help

2019-03-03 Thread Daniel Nicoletti
Em sáb, 2 de mar de 2019 às 10:58, Tamer Higazi escreveu: > > Dear Leo, > > The main problem is that the hardware already is with very poor specs. > You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM. Main problem!? Really!? He's on AWS of couse it's 64bits, 2 CPU cores is a

Re: [uWSGI] Help

2019-03-02 Thread Léo El Amri
Tamer, On 02/03/2019 14:58, Tamer Higazi wrote: > The main problem is that the hardware already is with very poor specs. > You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM. I think a two cores 4GB RAM server, as long as it is not running on 5MHz cpus should be more than

Re: [uWSGI] Help

2019-03-02 Thread Tamer Higazi
Dear Leo, The main problem is that the hardware already is with very poor specs. You have a dual core CPU (perhaps 32 bit even) and then with 4GB RAM. you want to provide services and even like to earn money with it, and start saving money on hardware. Why this nonsense ? Nobody said that you

Re: [uWSGI] Help

2019-03-02 Thread Léo El Amri
On 02/03/2019 14:04, Tamer Higazi wrote: > 2. And with your comment "So please help to scale the application for > concurrent users." > > is very unpolite. I think it was just badly written english. I don't think they meant to be unpolite. On 02/03/2019 14:04, Tamer Higazi wrote: > 1. Get

Re: [uWSGI] Help

2019-03-02 Thread Tamer Higazi
Dear Ashraf, 1. Get yourself propper hardware, that would solve perhaps by 80% your problems. 2. And with your comment "So please help to scale the application for concurrent users." is very unpolite. Nobody has to help you, and people in the open source world don't make support for

[uWSGI] Help

2019-02-28 Thread Ashraf Mohamed
Hi , I have a flask application which is running in nginx server and i am unbale to serve the application for more then 20 users (concurrently) as its gets break. *Error:* app: 0|req: 1/35] x.x.x.x () {44 vars in 5149 bytes} [Thu Feb 7 14:01:42 2019] GET

[uWSGI] help

2016-11-11 Thread Norbert Wasilewski
-- Forwarded message - From: Date: pt., 11.11.2016 o 17:23 Subject: Welcome to the "uWSGI" mailing list (Digest mode) To: Welcome to the uWSGI@lists.unbit.it mailing list! To post to this list, send your email to:

Re: [uWSGI] help with documentation

2015-10-19 Thread Riccardo Magliocchetti
Hello, Il 07/10/2015 15:07, Riccardo Magliocchetti ha scritto: Hello, i've started labeling issues on github that i think are documentation issues: https://github.com/unbit/uwsgi/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation They are quite a few and most of them take just a few minutes

[uWSGI] help with documentation

2015-10-07 Thread Riccardo Magliocchetti
Hello, i've started labeling issues on github that i think are documentation issues: https://github.com/unbit/uwsgi/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation They are quite a few and most of them take just a few minutes to fix. I've labeled everything that can help to avoid having

[uWSGI] [Help Needed] Cannot allocate memory

2015-02-06 Thread Poh Yee Hui
Hi, I would like to ask for some help regarding issues with memory allocation. This is the error that I have found in the log. malloc(): Cannot allocate memory [core/utils.c line 1781] !!! tried memory allocation of 1768781160 bytes !!! *** backtrace of 7276 *** *** end of backtrace *** This

Re: [uWSGI] [Help Needed] Cannot allocate memory

2015-02-06 Thread Roberto De Ioris
Hi, I would like to ask for some help regarding issues with memory allocation. This is the error that I have found in the log. malloc(): Cannot allocate memory [core/utils.c line 1781] !!! tried memory allocation of 1768781160 bytes !!! *** backtrace of 7276 *** *** end of backtrace ***

Re: [uWSGI] [Help Needed] Cannot allocate memory

2015-02-05 Thread Poh Yee Hui
My uWSGI configuration is as follow. [uwsgi] socket = /var/run/uwsgi/myapp.sock ;http = :8080 stats = 127.0.0.1:9191 pidfile = /var/run/uwsgi/myapp.pid daemonize = /var/log/uwsgi/myapp.log log-slow = true master = true chdir = /srv/myapp wsgi-file = /srv/myapp/main.py processes = 4

[uWSGI] [Help Needed] Cannot allocate memory

2015-02-04 Thread Poh Yee Hui
Hi, I would like to ask for some help regarding issues with memory allocation. This is the error that I have found in the log. malloc(): Cannot allocate memory [core/utils.c line 1781] !!! tried memory allocation of 1768781160 bytes !!! *** backtrace of 7276 *** *** end of backtrace *** This

Re: [uWSGI] [Help Needed] Cannot allocate memory

2015-02-04 Thread Roberto De Ioris
Hi, I would like to ask for some help regarding issues with memory allocation. This is the error that I have found in the log. malloc(): Cannot allocate memory [core/utils.c line 1781] !!! tried memory allocation of 1768781160 bytes !!! *** backtrace of 7276 *** *** end of backtrace ***

Re: [uWSGI] Help with nginx prematurely closed connection error (Django app)

2013-07-23 Thread Łukasz Mierzwa
I thought that subscriptions packet were UDP based, my --fastrouter-subscription-server option spawns UDP socket. @Cycle switch from file sockets in fastrouter-subscription-server and subscripe2 options to port based ones. 2013/7/23 Roberto De Ioris robe...@unbit.it On 23/07/13 13:43,

[uWSGI] Help with the --reaper option for experienced uwsig users?

2012-10-22 Thread Andrew Fischer
I've been running uwsgi for about a year and I've run into a situation that I can't seem to sort out. I'm not positive there is a good solution, but maybe someone with far more knowledge than I could shed some light. I'll give some background, please bear with me. I run uwsig behind nginx to run

Re: [uWSGI] Help with the --reaper option for experienced uwsig users?

2012-10-22 Thread Andrew Fischer
Sorry, I meant to say at the end I realize uwsgi is not the problem here; I blame *hgweb* and buildbot. -Andrew On Mon, Oct 22, 2012 at 9:14 AM, Andrew Fischer wizzr...@gmail.com wrote: I've been running uwsgi for about a year and I've run into a situation that I can't seem to sort out. I'm

Re: [uWSGI] Help with the --reaper option for experienced uwsig users?

2012-10-22 Thread Łukasz Mierzwa
2012/10/22 Andrew Fischer wizzr...@gmail.com: However, I recently added buildbot to our setup, which is triggered by a commit hook in hgweb. It's all built in stuff, I didn't write any of it. Do You use this hook:

Re: [uWSGI] Help with the --reaper option for experienced uwsig users?

2012-10-22 Thread Roberto De Ioris
Il giorno 22/ott/2012, alle ore 16:14, Andrew Fischer wizzr...@gmail.com ha scritto: I've been running uwsgi for about a year and I've run into a situation that I can't seem to sort out. I'm not positive there is a good solution, but maybe someone with far more knowledge than I could shed

Re: [uWSGI] Help me please with accessing cache between 2 instances

2012-05-22 Thread test157
Hello Roberto, I'am getting this error while using it on the same machine, so I don't use it over the network. ___ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

[uWSGI] Help me please with accessing cache between 2 instances

2012-05-19 Thread test157
Hi everyone. I have 2 uwsgi instances 1. the first one is running at 127.0.0.1:10001 with cache = 1000 (reads/writes cache) 2.the secondisrunning at 127.0.0.1:10002 with cache = 1 (reads/deletes values only from the first instance) when I'am trying to access cache,