Limitations of Phoenix Traces in RAM: Server/UI Capacity Explained

·Apr 19, 2024 09:05 PM

Quick question: right now Phoenix traces are all saved in RAM, right? Is there a specific limit for the server/web ui itself ? How much can it handle?

5 comments

· Sorted by Oldest

Xander S.
·
Hey Marcelo d., we don't impose a limit on how much memory Phoenix can consume. I don't know if we've really pushed it to the limit to see how much it can really handle, and presumably, it depends on the hardware it's running on. Worth noting that persistence is coming in about two weeks, this sort of limitation will not exist for much longer.
Marcelo d.
·
Oh that's great! Thanks Xander S.!
👍1
Sean L.
·
Nice, so which persistence options are under consideration? perhaps elasticsearch?
👋1
Xander S.
·
By default, Phoenix will run with an embedded SQLite. We will also support Postgres.
👍2
Sean L.
·
Got it. Thank you!
🫡1

Xander S.
·
Hey Marcelo d., we don't impose a limit on how much memory Phoenix can consume. I don't know if we've really pushed it to the limit to see how much it can really handle, and presumably, it depends on the hardware it's running on. Worth noting that persistence is coming in about two weeks, this sort of limitation will not exist for much longer.
Marcelo d.
·
Oh that's great! Thanks Xander S.!
👍1
Sean L.
·
Nice, so which persistence options are under consideration? perhaps elasticsearch?
👋1
Xander S.
·
By default, Phoenix will run with an embedded SQLite. We will also support Postgres.
👍2
Sean L.
·
Got it. Thank you!
🫡1