In case of issue, this time you'll have a lot more log to share ^^
can I fix that by adjusting
s_heartbeatInterval and/or s_heartbeatTimeout?
Those aren't used right now. The driver solely depends on server side heartbeat protocol (might add it for the next version). So those would have to be set on the server itself for now.
Before that. Are you under a heavy workload ? If yes, it might be a good call to increase those values.
Also, make sure you'll also running your application with -threaded GHC options. If under heavy workload, the driver will be slower if it doesn't run on all your cores
might be a very slow server
I really don't get these "slow bus msg" log entries
ghc-options: -threaded -rtsopts -with-rtsopts=-N
should be good
(~130k events)
but re this "issue": should I investigate this or just wait for the major refactoring; it's probably already fixed there
I hate this uncertainty about whether I fucked up the server, the app, the store or if it's something in the driver xD
generally it's when it takes more than 200ms
but it changes depending on which queue is it
that's not an issue
guess that works
kinda ugly
:D
and I'm on too many chat programs already xD
okay, I try to have another look at the subscription implementation
Is there eventstore/eventsource discord channel somewhere, that's what you're asking ?
but that would mean 2 chats
you can just DM in Discord though
also there is this FP discord
nice ppl from what I can tell
have to reset my password, long time since last time I used Discord
^^
better than Slack if you ask me
and it has fun stuff like looking up gifs
This channel is no longer supported, please join us in our new Discord server: https://discord.gg/x7q37jJ