Get/ show messages stored in MemoryCallQueue?

#1

Hi,

quick question: is there any way to look into the MemoryCallQueue (from realmstore.py) and see how many and which messages are stored in them?

Thanks!

Jan

0 Likes

#2

Hi,

Hi,

quick question: is there any way to look into the MemoryCallQueue (from
realmstore.py) and see how many and which messages are stored in them?

You mean call queuing as in

https://github.com/crossbario/crossbar-examples/tree/master/scaling-microservices/queued

?

If so, then no, currently, there is no Crossbar.io meta API to get your hands on these internal queues ..

What's the use case?

Cheers,
/Tobias

···

Am 21.03.2017 um 14:00 schrieb John Doe:

Thanks!

Jan

0 Likes

#3

Hi Tobias,

yes, I based it on https://github.com/crossbario/crossbar-examples/tree/master/scaling-microservices

The event history also doesn’t help me then, I guess? https://github.com/crossbario/crossbar-examples/tree/master/event-history

Use Case (its a private project):

  • multiple callers
  • a few callees which register a rpc with concurrency=1, every call takes a few seconds
  • I trigger a few thousand request, which fill up the queue

For monitoring, I would now like to watch the queue shrink and grow. Also I’m wondering how much memory it comsumes and if there’s a hard limit.

Regards,
Jan

···

Am Dienstag, 21. März 2017 15:16:09 UTC+1 schrieb Tobias Oberstein:

Hi,

Am 21.03.2017 um 14:00 schrieb John Doe:

Hi,

quick question: is there any way to look into the MemoryCallQueue (from

realmstore.py) and see how many and which messages are stored in them?

You mean call queuing as in

https://github.com/crossbario/crossbar-examples/tree/master/scaling-microservices/queued

?

If so, then no, currently, there is no Crossbar.io meta API to get your
hands on these internal queues …

What’s the use case?

Cheers,

/Tobias

Thanks!

Jan

0 Likes

#4

Hi Jan,

The event history also doesn't help me then, I guess?

nope, that's a different animal

Use Case (its a private project):
* multiple callers
* a few callees which register a rpc with concurrency=1, every call takes a
few seconds
* I trigger a few thousand request, which fill up the queue

For monitoring, I would now like to watch the queue shrink and grow. Also

I see. Please file an issue on the Crossbar.io repo giving as much context / motivation / use case description as you can.

The feature could be done in the context of the meta API of Crossbar.io.

Get queue size, get meta events whenever the queue expands/shrinks etc etc

I'm wondering how much memory it comsumes and if there's a hard limit.

The limit (queue size) is configurable.

The hard limit is of course your available RAM;)

The amount consumed will be roughly: N x payload_size

where N is the number of queued calls, and payload_size depends on args/kwargs in your calls

Note: currently, this is also completely in-memory. We also want to have a LMDB option, and that would mean:

- RAM doesnt matter
- persistency over router restarts

However, don't hold your breath .. we have a massive backlog of stuff to do and feature requests .. though you could throw money at us to move it up the backlog;)

Cheers,
/Tobias

···

Regards,
Jan

Am Dienstag, 21. März 2017 15:16:09 UTC+1 schrieb Tobias Oberstein:

Hi,

Am 21.03.2017 um 14:00 schrieb John Doe:

Hi,

quick question: is there any way to look into the MemoryCallQueue (from
realmstore.py) and see how many and which messages are stored in them?

You mean call queuing as in

https://github.com/crossbario/crossbar-examples/tree/master/scaling-microservices/queued

?

If so, then no, currently, there is no Crossbar.io meta API to get your
hands on these internal queues ..

What's the use case?

Cheers,
/Tobias

Thanks!

Jan

0 Likes