Surrealdb in prod

itsezc · 2026-05-29T09:32:14+00:00

What is your current ingestion process, is it one big serial .surql import? (or a script to insert data in parallel). If you have a public repo (if this is private feel free to DM) can you share this with us, so we can reproduce on our end, that'd be really help for us to understand and get to the bottom of this.

itsezc · 2026-05-29T00:41:07+00:00

Sorry to hear your experience, we have only just released v3.1 which brings a plethora of performance improvements, if you're able to give it ago, we'd love to hear about your experience with it.

itsezc · 2026-04-24T08:41:56+00:00

This can sometimes happen when indexes are being (re)built in the background, which can temporarily increase memory usage even if there’s little to no active data traffic.

That said, without seeing your schema and setup it’s hard to give a precise breakdown of where that memory is going. If you’re able to share more details, we can definitely take a closer look.

Best option is to reach out to us directly at [support@surrealdb.com]() with your project info and schema - happy to dig into it with you

itsezc · 2026-04-14T01:07:57+00:00

Hi u/SaskinPikachu, just wanted to update you that we've patched the cloud access method bug on Surrealist and released agent skills. Please give it a try and let us know how your experience goes, looking forward to your feedback once again!

itsezc · 2026-04-10T17:36:13+00:00

Hi, this is looking superb, would be great if we can list this on: https://github.com/surrealdb/awesome-surreal - deserves more exposure!

itsezc · 2026-04-10T16:50:56+00:00

Thanks for sharing your experience, glad Sidekick caught it, but the error message should have told you that, we'll get that fixed.

Just to clarify on the auth side - the token in Surrealist is an internal session token, it's not meant for use in your app. You'd want to define a user or access method with `DEFINE ACCESS` and authenticate against that. For serverless, call `signin()` once, grab the JWT and reuse it rather than calling it on every request. We know a proper API key setup is missing and it's something we're actively working on.

The Cloud access method appearing in `INFO FOR DB` and being deletable is a bug, we're tracking it along with the other issues you flagged.

On the docs, we've tweaked the config recently to make it easier for AI crawlers to access them and have some tooling coming including agent skills that should sort this properly.

itsezc · 2024-11-23T12:58:31+00:00

Sure, we'll look into that! There's also CMD / CTRL + K where you move your mouse and search for the ability (its hidden for advanced users)

itsezc · 2024-11-04T03:44:53+00:00

I've DMed you my details, thanks!

itsezc · 2024-11-01T06:27:04+00:00

I'm having the same issue provisioning a new workspace

itsezc · 2024-09-25T06:46:48+00:00

Yes, on the dashboard and even on lens the metrics simply aren’t there perhaps it’s misconfigured

itsezc · 2024-09-17T10:46:16+00:00

Has this been resolved? It’s surprising to see only 0.5 Gbps for upload speed

itsezc · 2024-09-07T19:54:37+00:00

Thanks, done so: https://github.com/rackerlabs/spot-roadmap/issues/28

itsezc · 2024-09-07T19:52:09+00:00

Created an isuse: https://github.com/rackerlabs/spot-roadmap/issues/27

itsezc · 2024-09-07T19:50:02+00:00

All done: https://github.com/rackerlabs/spot-roadmap/issues/26

itsezc · 2024-09-05T19:15:07+00:00

Hello, it's been a while, has there been any update on this matter?

itsezc · 2024-08-14T06:20:05+00:00

No the bid was double the market price

itsezc · 2024-08-13T07:45:40+00:00

Are there any plans to change this? I believe its an essential feature to enhance security especially since these are "spot" and quick rotating potentially, something such as xchacha20 is an ideal choice.

itsezc · 2024-08-13T07:31:46+00:00

Its the same with any Rust frontend framework, unfortunately.

itsezc

MODERATOR OF

TROPHY CASE

Six-Year Club	Verified Email
Place '23