| Re: [mosquitto-dev] Mosquitto V1.3.5 - short HIGH CPU |
Will the server be able to handle 1024*2 or is this limit per server on the WSAPoll...sounds like the limit is 1024 no matter how many instances :(Lets say I start a mosquitto broker to listen on port 9000 and another mosquitto on port 8000 - same serverHi RogerOn that note - regarding the 1024 limit
I am doing various tests on this side and man oh man, Mosquitto is really powerful MQ Broker - fast, config dead simple and low on resources :)Do we see the same limitation on Linux?On Mon, Oct 13, 2014 at 6:01 PM, Roger Light <roger@xxxxxxxxxx> wrote:Hi Izak,
The WSAPoll() function on Windows limits you to listening to 1024
sockets at once, nothing more complicated than that. Future versions
of mosquitto should make use of the IOCP API on Windows (through a
portable library) which would remove that limitation.
Cheers,
Roger
On Mon, Oct 13, 2014 at 4:16 PM, Oegma2 <oegma2@xxxxxxxxx> wrote:
> Hi Roger
>
> Thanks for getting back so quick - I am not sure what else to do regarding
> the V1.3.5, but the fact that I can only handle about a 1000 on a windows
> server tells me I need to make a plan - if I run this broker on a Linux
> server, will that allow me more than 1000 clients? We are looking at about
> 10 000 clients per server, if we can get 50 000 clients per server, even
> better :)
>
> The current V1.2.3 broker is not using CPU or RAM at all - with already 100
> clients connected...is there a reason why we can only get 1000 clients on a
> windows server?
>
>
> On Mon, Oct 13, 2014 at 5:05 PM, Roger Light <roger@xxxxxxxxxx> wrote:
>>
>> Hi Izak,
>>
>> I'm afraid that it's impossible to say without more details.
>>
>> Not entirely related, but are you aware that on Windows only around
>> 1000 clients are possible per broker?
>>
>> Regards,
>>
>> Roger
>>
>>
>> On Mon, Oct 13, 2014 at 1:36 PM, Oegma2 <oegma2@xxxxxxxxx> wrote:
>> > Hi
>> >
>> > I've upgraded my server from Mosquitto V1.2.3 to V1.3.5 and since then,
>> > the
>> > CPU usage for mosquitto jumps to 100% for short time and then back to 0%
>> > or
>> > very very little cpu usage
>> >
>> > This happens quickly but i am worried that if we add more units with a
>> > system that push the cpu to 100% and back can eventually lock @100% CPU.
>> > I
>> > reverted back to V1.2.3 for now
>> >
>> > Any idea why that will happen?
>> >
>> > My server is small windows 2008, 1 CPU, 4 gig ram server for a reason -
>> > to
>> > make sure our code and system run correctly before we go to production
>> > servers :) and hide issues with loads of ram and cpu
>> >
>> > I want to thank the dev team for the time, effort and dedication with
>> > Mosquitto, it's an awesome broker and hope one that will stay around for
>> > a
>> > long time
>> >
>> > Warm regards
>> > Izak Smit
>> > Senior Software Engineer
>> >
>> >
>> >
>> > _______________________________________________
>> > mosquitto-dev mailing list
>> > mosquitto-dev@xxxxxxxxxxx
>> > To change your delivery options, retrieve your password, or unsubscribe
>> > from
>> > this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
>> _______________________________________________
>> mosquitto-dev mailing list
>> mosquitto-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
>
>
>
> _______________________________________________
> mosquitto-dev mailing list
> mosquitto-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev