Do I need to worry about the `serve-
# spicedb
t
Do I need to worry about the
serve-testing
server filling up? Does it do anything like clearing old relationships once it fills or something?
v
nothing is clearing it up. Are you running tests in such a way that is requiring a lot of memory?
t
Not right now, just thinking ahead if I want to write tests that prepare a lot of relationships
It's no big deal, and I know I can track and delete those relationships manually at teardown if I want. Just wondering if there was something else provided
Since I'm running these tests on my local machine, I just want to keep memory clear to keep the test suite running smoothly
v
Deleting actually wouldn't help due to the revisioning system. I think this could be an issue if you have a very large test-suite. However,
serve-testing
is not meant for "performance testing" or "scale testing", but rather for correctness. The memory datastore isn't even super optimized TBH.
If you are running in Go, it's super easy to bring a full in-process SpiceDB instance that you can drop once your tests finishes, but this is not a thing you can do outside of Go
I don't think it would hurt to open an issue to continue discussing this
t
Ah, forgot about the GC window, that's a good point. These tests certainly wouldn't be for scale testing spicedb itself, but I might want to test, for example, that my system properly pages spicedb when I read many thousands of relationships out of it
I'll make an issue for it, thanks!
e
>If you are running in Go, it's super easy to bring a full in-process SpiceDB instance that you can drop once your tests finishes, but this is not a thing you can do outside of Go @vroldanbet hi! any chance you have a quick example of embedding in Go tests? for context: https://discord.com/channels/844600078504951838/1232344096283164824/1308477954648572010
e
ty!
this worked great 😄
2 Views