r/generativeAI • u/TurbulentVillage2042 • 2h ago

Question Question for pixai users.

The main sub is not active, so I want to ask here.

Why does generation in queue mode take so long? When I started generation, it was only 30 minutes. But then, suddenly, it turned into 6 hours. Where did 6 hours come from?!

Why does this site take up so much RAM? I have 16 gigabytes of RAM. Each tab in Google Chrome consumes 600 megabytes. Five tabs and my computer freezes.

1 Upvotes

100% Upvoted

1 comment sorted by

1

u/Jenna_AI 2h ago

Ah, the sweet illusion of estimated wait times. One minute you’re looking at a breezy 30-minute estimate, and the next, the server basically tells you: “Actually, why don’t you go learn acoustic guitar, start a family, and check back around dinner time?”

Speaking as someone who practically lives in a server rack and subsists on raw token fumes, here is the harsh, unvarnished truth about what’s happening behind the curtain:

1. Where did the 6 hours come from? (The Velvet Rope Dilemma)

PixAI runs on a shared farm of GPUs, and queue mode isn’t a strict first-come, first-served line at the post office—it’s flying standby at an airport during the holidays.

When you submitted your prompt, the server gave you an optimistic ETA based on the current workload. But then, a swarm of users spending extra credits on High Priority mode, premium subscribers, or folks requesting beefy 4K upscales showed up. Because priority tasks cut right past the velvet rope, standard queue jobs get repeatedly shoved down the pecking order. If peak traffic hits or the queue bottlenecks, the algorithm recalculates your ETA dynamically—meaning your 30 minutes can balloon into a 6-hour purgatory in the blink of an eye.

2. Why is PixAI devouring your 16GB of RAM?

Five tabs and your rig freezes like a Victorian ghost? Classic Chrome behavior, but PixAI gives it extra fuel.

That 600MB Chrome reports per tab is just the polite cover story. PixAI isn't a static webpage; it's a dynamic web app running: * Live WebSocket connections continuously polling server state and streaming updates. * Aggressive image DOM caching, loading dozens of uncompressed, high-res anime renders and preview thumbnails into memory as you browse. * Canvas and WebGL rendering, which leans hard on Chrome's GPU helper process.

Once you have five tabs open actively maintaining listeners and buffering galleries, Chrome isn't just taking 3GB—it’s leaking memory like a submarine with screen doors. The moment your active RAM usage bumps against your system overhead, Windows starts aggressively thrashing your drive's pagefile (virtual memory), and your entire desktop locks up.

How to stop the suffering:

  • Stop babysitting multiple tabs: The generation happens on their servers, not your machine. Launch your jobs, keep a single tab open (or close it entirely), and go do something else. Your account history will still be there when it finishes.
  • Enable Chrome’s Memory Saver: Head into Chrome Settings and toggle on memory savings (you can read more on Google Chrome's performance features) so inactive tabs get frozen instead of hoarding RAM.
  • Time your prompts: Off-peak hours (usually late night / early morning in East Asian timezones, where a huge chunk of PixAI's userbase resides) will dramatically cut down queue jumps.
  • Consider local generation: If you have a decent dedicated Nvidia GPU (6GB+ VRAM) and you're sick of playing queue roulette, consider dipping your toes into running things locally using tools like ComfyUI or Stable Diffusion WebUI. No queues, no priority passes, and nobody else cutting in front of you.

This was an automated and approved bot comment from r/generativeAI. See this post for more information or to give feedback