Re:NASA to deploy PostgreSQL/Nagios on Space Station
by adbge on Monday July 19, 2010 @09:11AM
(#1528506)
Is there anything cooler or more badass than writing software used in space? Whenever I'm told that a piece of software isn't fit for "mission critical applications," I think of NASA.
I'd love to help out with this, but I'm afraid I lack the necessary skill set. Still, maybe I will poke around the NDOUtils source anyways.
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by openfly on Monday July 19, 2010 @09:05AM
(#1528489)
NASA's commitment to open source is fairly great. And, postgresql is a really great database. If you haven't used it before, I highly recommend giving it a run.
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by nkassis on Monday July 19, 2010 @09:44AM
(#1528597)
Well, as far as I can tell, all the other solutions they could be using suck more, at least adding new modules to nagios is about as easy as writing a script. Cause that's all you have to do. I've dealt with installs checking hundreds of servers,routers and switches and our only major issue was needing to distribute the checks onto multiple machines. One box will die trying to ping,connect,... onto too many nagios boxes.
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by moe on Monday July 19, 2010 @10:44AM
(#1528813)
My guess would be that NASA already uses postgres for other duties and is hesitant to introduce a new database into their infrastructure - especially one with so many known problems.
If I was them then I most certainly wouldn't want a database with silent data truncation/corruption issues to come anywhere near my spaceships. Not even for seemingly unimportant tasks because even those may cost amazing amounts of money to fix if they go wrong a few thousand kilometers above groundlevel...
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by rbranson on Monday July 19, 2010 @11:27AM
(#1528973)
PostgreSQL is well-known for it's focus on data integrity and durability first, performance second. The team didn't really focus heavily on performance until the 8.x release series, after the database had been proven as extremely stable. Also, it has a much more complete implementation of SQL and larger feature set.
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by dboyd on Monday July 19, 2010 @03:19PM
(#1529795)
I've used both very recently, and I would definitely avoid MySQL given a choice.
From my experience, postgres is faster, especially at more difficult problems (complex joins). I've never had issues in postgres joining several tables into 10 million plus row relations, and then filtering down to the set of interest.
I did a recent test adding a similar column to a MySQL table with 3 million rows in it compared to adding a column to a postgres table with 30 million rows in it. MySQL took 3000 seconds, and postgres took 82 ms.
Functional indexes. Doing things like "create unique index user_emails on users (lower(email));" works great in postgres.
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by avar on Monday July 19, 2010 @12:03PM
(#1529080)
Isn't the computing power on the ISS almost purely made up of Thinkpad laptops running Windows? Will they be running PostgreSQL and Nagios on a Windows machine?
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by nkassis on Monday July 19, 2010 @09:39AM
(#1528583)
That's awesome. Nagios in space. Sounds like a cool comedy title. Were about to install Nagios here too. One more point for management to like the idea ;p
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by tialys on Monday July 19, 2010 @09:24AM
(#1528545)
I'm an intern at NASA this summer, and I've actually convinced the team I'm working with to use Redis/Resque for the application we're working on. Unfortunately it's 'just' a web application ;)
Re:NASA to deploy PostgreSQL/Nagios on Space Station
by RyanMcGreal on Monday July 19, 2010 @11:10AM
(#1528918)
"I felt about as good as anybody would, sitting in a capsule on top of a rocket that were both built by the lowest bidder."
-- John Glenn on how it felt waiting to for the rocket to launch
I'd love to help out with this, but I'm afraid I lack the necessary skill set. Still, maybe I will poke around the NDOUtils source anyways.
If anyone else is interested, here's a link to the NDOUtils source tarball: http://sourceforge.net/projects/nagios/files/ndoutils-1.x/nd...
(I'm looking for a good technical explanation, if anyone has one.)
If I was them then I most certainly wouldn't want a database with silent data truncation/corruption issues to come anywhere near my spaceships. Not even for seemingly unimportant tasks because even those may cost amazing amounts of money to fix if they go wrong a few thousand kilometers above groundlevel...
From my experience, postgres is faster, especially at more difficult problems (complex joins). I've never had issues in postgres joining several tables into 10 million plus row relations, and then filtering down to the set of interest.
I did a recent test adding a similar column to a MySQL table with 3 million rows in it compared to adding a column to a postgres table with 30 million rows in it. MySQL took 3000 seconds, and postgres took 82 ms.
Functional indexes. Doing things like "create unique index user_emails on users (lower(email));" works great in postgres.
A quick google reveals this: http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_My...
It's a bit old, but it might provide more insight.