Coronium Feedback

[Develephant]

@anaqim

Hi dev,

I’m stress testing my app a little and notice that the coronium api is giving me some callback errors.

Checking digitalocean error codes, it seems to me that these codes are not from them.

I get the following after sending some 45 requests to do sql.insert, each call made from the client with a 100 ms delay between.

“309 Request rate exceeded”

“250Request rate exceeded”

This is not a concern if this is a limitation on a per user basis, but if it is on a per app/server basis, im in trouble.

Do you know anything about this?

EDIT - Checked the core logs and found this

[error] 1591#0: *147941 limiting requests, excess: 20.170 by zone “apilimit”, client: xx.xx.xx.xx, server: , request: “POST / HTTP/1.1”, host: “xx.xx.xx.xx:10001”

Hi,

The limit is per client/IP.

If you’d like to remove or adjust it I can walk you through that.

-dev

[Develephant]

@anaqim

Hi dev,

A second issue just popped up which I’d call a bug.

Your new mysql.insertMany works fine but is unable to handle a single record, something I think it should be able to handle due to the dynamic nature of it all.

Hi,

Thanks for the report. I will take a look at it and make some adjustments.

Go ahead and start new forum topics for new issues/requests. It will make it easier for me to track. 

I appreciate the feedback!

-dev

[anaqim]

@Develephant

Hi,

The limit is per client/IP.

If you’d like to remove or adjust it I can walk you through that.

-dev

Thats a relief 

From your reply can I assume the reason for this limir is more of a practical nature than technical?

Wouldnt that be possible to have as a variable somewhere, like the network timeout parameter you fixed?

Like “Max API calls per sec” or something

I know I ask a lot but I love your product and cant hold back on opinions. 

[Develephant]

Hi,

Feedback is the driving force for Coronium, so I’m always open to suggestions. 

The request limit is there to help mitigate a client from ‘spamming’ the server, either by programmatic mistakes, or otherwise.

Making that dynamic is a little more tricky, but I’ll see what I can some up with. Right now it’s set kind of low, so I might boost it a bit in the next update.

-dev

[anaqim]

@Develephant

Hi,

Feedback is the driving force for Coronium, so I’m always open to suggestions. 

The request limit is there to help mitigate a client from ‘spamming’ the server, either by programmatic mistakes, or otherwise.

Making that dynamic is a little more tricky, but I’ll see what I can some up with. Right now it’s set kind of low, so I might boost it a bit in the next update.

-dev

I see your point.

Perhaps setting the threshold a little higher might be enough, like once per 100 ms might be reasonable or something?