Also, say I am in a group of 1000 people, and I send a message - does that equal to 1000 messages? As the server needs to send a message to each participant.
You can find the limit for number of messages per second depending on plan here: http://quickblox.com/plans/
As for "does hat equal to 1000 messages?" - it depends on the code (plartform) you are using.
Related
I have a system A (generating messages each 1 second) linked over WSO2 EI with a system B (REST API).
The system B does not need so much data and it would be enough to send only each 60th message (so to speak kind of sampling).
could you please, tell me how to send out only each "x" message in the WSO2 EI?
Either time based (e.g every 60 sec) or count based (each 100th message)?
thx a lot!
Not sure, but maybe the following will work for you.
Store a counter value somewhere (e.g. database)
When system A generates a message, read that value from store
(database)
Increase that value and store it (e.g. databse)
Check if counter modulo 60 = 0
If so, send to system B otherwise do nothing
This should be possible using db mediator, script mediator and filter mediator.
Hope that helps.
I am trying to understand latency vs maximum number or requests that can be served per second.
What I understood RTT is time taken for message to reach destination and acknowledgement back to source. So I assume server can only serve maximum requests per second should not exceed more then sum of avg round trip in a give second. My local ping test shows as
> ping 127.0.0.1
rtt min/avg/max/mdev = 0.089/0.098/0.120/0.012 ms
on average it takes 0.098 ms just for network round trip, which means 10 ping req/ms. So I assume that in sequential order a client can only execute maximum of 10_000 req/sec. while it turns out I am wrong. redis-benchmark tool shows something different.
> redis-benchmark -t set -c 1 -h 127.0.0.1
====== SET ======
100000 requests completed in 2.53 seconds
1 parallel clients
3 bytes payload
keep alive: 1
100.00% <= 1 milliseconds
39588.28 requests per second
a single client is able to execute 39 req/ms while i am expecting maximum of 10req/ms.
Can anyone help me where I went wrong or misunderstood ?
Commands can be pipelined even when using a single logical client thread, meaning: you can send lots of requests before the first response comes back. Responses always come back in request order (unless you're using pub/sub), so a pipelining client simply needs to keep a queue of sent messages that have not yet seen responses, and pair responses to requests as they arrive.
So: you aren't strictly bound by latency, although that remains a useful number. The raw throughout number (bound by bandwidth and server capacity) is also meaningful, since it is often the case that you want to issue multiple commands.
what is BestBuy API call limit for the product details? How many calls per hour/day ?
The default call limits for approved accounts is 5 queries per second/50,000 queries per day. If you surpass these limits, you will receive a 429 error code with an error response stating quota limit exceeded.
Just for anyone who runs across this question the error code has changed to 403. Source: https://bestbuyapis.github.io/api-documentation/#errors
The default call limits for approved accounts is 5 queries per second or 50,000 queries per day. If you go pass this limits, you will receive an error code with an error response saying that you have exceeded the quota limit. The error code number is 429.
I am trying to gather a range of messages through the rest API, and am aware that you can only retrieve 20 results at a time. I have tried incrementing a page variable, but this has no affect, and I am just getting the same results each time no matter the page number (https://www.yammer.com/api/v1/messages.json?page=6). I have proceeded to use the newer_than and older_than parameters to page through the results, and it works to some extent, but it appears to be excluding records. I am using the following approach below:
Since just setting a newer_than only results in the 20 most recent records as long as they are newer than the id that is sent in the newer_than parameter, I am also setting a dynamic older_than parameter.
Send request with only a newer than parameter. This returns the 20 most recent records. (eg. ww.yammer.com/api/v1/messages.json?newer_than=235560157)
Extract the ID of the 20th id in the JSON, and using this to populate the older_than parameter. The result is 20 different records. (eg.ww.yammer.com/api/v1/messages.json?newer_than=235560157&older_than=405598096)
Repeat step 2 until no results are returned since the newer_than and older_than parameters will eventually overlap.
The problem is that the set of records that is returned with this method is less than the number of records that is returned for messages from the data export API. I am working under the assumption that newer message IDs are always generated with a value greater than any older messages.
Could I possibly be misunderstanding how paging through results is supposed to be implemented with the REST API?
Any help would be much appreciated!
Thanks in advance!
First of all, the page parameter works only for the search API.
Secondly, the way you are trying to fetch messages will not return any comments on the messages or will return top 2 comments on any message based on the "extended" parameter. By default it returns 2 comments on every message. To get all the comments on the message you will have to get it individually message wise.
That must be causing the difference in the number of messages in the two methods mentioned.
I agree with Farhann - The rest API endpoint returns only top two comments for any message by default. To get all the comments for a post, you have to make a separate request.
With the use of the Data Export API, all the comments along with the message (public and private) are also exported which increases the count of the number of the messages. While, the API call returns only recent 2 comments on any message by default.
The data export includes private messages. Private messages will not be returned by that API call.
Check if the messages you are not seeing are private messages.
Looking at the documentation i found this information :
Data Extraction API requests are rate limited by number of requests and data download volume per unit of time (hour, day, week, or month). If you exceed the limit, a 403 error occurs.
Someone could tell me more about this limit ? How many call per day/month/year ???
Just spoke to webtrends support. The limit is 600 requests per use per hour or 1 Gig per user per hour.