We had perl-scripts hammering millions of new rows into our newly designed DB-Server, many of them running in parallel. The DB-Server strikes back now: It's running a postgres-thread eating up around 1 Gig RAM and 90 percent cpu-time. I don't know what's happening deep inside the db, i don't even know how to find out. i'm learning new stuff everyday but i'm still far from beeing a postgresql-geek.
I suspended the perls, giving postgres a few hours to sort things out.
I'm praying for a smll little knowledgable ghost helping out with database-design and operating. But I'm afraid I'll have to keep learning by failing, the hard way.
tom
Subscribe to:
Post Comments (Atom)
4 comments:
You need to apply the Highlander solution ("there can be only one") to your Perl program. See http://www.stonehenge.com/merlyn/WebTechniques/col54.html for the details.
Super blog, j'adore vos articles et reportages, bonne continuation.
voyance sérieuse gratuite par mail
Très bon blog et merci d'en faire profiter.
voyance mail rapide
Thanks to you, I learned a lot of interesting things. I hope to learn more. I congratulate you for these wonderful shares. Keep going !
voyance discount gratuite
Post a Comment