IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Interbase "seen" as going away...
It can't. It's an open source project now. It will always be as available as MySQL or Postgres.

As to postgres being more complex, I will most certainly disagree there. It's amazingly simple to set up and easy to use, especially if you are used to Oracle.

The Sun/Linux testing was done by another company we're dealing with, in single machines. The basis was servlet and JMS load testing. The IO coming out of the linux box was much higher.
Regards,

-scott anderson
New Re: Interbase "seen" as going away...
> It can't. It's an open source project now. It will always be as
> available as MySQL or Postgres.

It takes a certain amount of critical mass to ensure the long
term viability of any open source project. I certainly won't
be bug fixing Interbase, and unless there is a critical reason
to go with it as opposed to any other, I'd choose the other.

> As to postgres being more complex, I will most certainly disagree there.
> It's amazingly simple to set up and easy to use, especially
> if you are used to Oracle.

Just a simple issue of preference, I guess. I've done both.
Since I lived in Oracle for many years. I can deal with it's
complexity without blinking. I can even explain it to others.
On the other hand, stupid simple stuff escaped me with
PostGreSQL, and I even have the Elephant book. I might be
prejudiced against it, though, after speaking to the marketing
slime at Great Bridge. I'm happy to see that tank, simply
because they were bullshitting on the benchmarks. I met them
at 'something'-XPO in NY last year. When I called them on
it, they agreed that the marketing guys pushed a bit.


> The Sun/Linux testing was done by another company we're dealing
> with, in single machines.
> The basis was servlet and JMS load testing. The IO coming out of
> the linux box was much higher.

Highly unlikely. I can consistently pump 180MB per second via 2
FC channel cards, and actually process the data as opposed to
spinning on the IO. On the other hand, until very recently, Intel/AMD
CPUs were MUCH faster than SPARC. So if you had a CPU intensive process
(which includes Java interpretation), you'd bottleneck on the CPU
before the IO, but if you were measuring the IO, it would "look"
slower. Did you do simultaneous CPU measurements during these tests?

And are you sure the bottleneck wasn't in what was feeding you
the data?

Also, since you were 'servlet' testing, were you network bound?
When going Sun->Sun, I can move about 75MB (mega BYTE) per
second via GB ethernet. When a Linux box gets in the mix
(Dual PIII-866 I think) the performance drops to about 30MB
per sec, and I see the Linux CPU spinning on the packets.

I'm comparing 3 CPU Sun 450s with Dual CPU Linux boxen here.
In most cases, the Linux box is faster on CPU but slower on IO,
so I end up buying a central 450 for the IO, and a stack of
Linux boxes as compute servers.

I usually always have a few performance windows up when I am
working on a box. 'top', 'iostat', 'ddu_watch (shows disk utilization,
simple df script). I can 'feel' when my disks start to get overloaded,
and I have the same processed running on Intel/Linux and Sparc/Solaris,
which means I usually spot bottlenecks very fast.

New PostGreSQL setup/complexity
I was wrong, or it has gotten a lot better.
Took the RPMs, followed the docs, and had
the large table loading in about 10 minutes.
New Yep.
I like Postgres a lot. I know it's not anywhere near what you'll be doing, but we've had nary a skip here on zIWT from the postgres stuff (once I decided to start vacuuming the database every once in a while :-).
Regards,

-scott anderson
New Re: Yep.
I'm on my 1st vacuum after creating 6 indexes.
How long should it take?
New Shouldn't need one right away.
It's for recalculating index distributions and the like. Kind of a waste right after indexing... :-)

I wouldn't know how long that much data would take. The zIWT tables aren't all that large yet.
Regards,

-scott anderson
     MySQL vs Oracle question - (broomberg) - (23)
         Other things to consider: - (admin) - (14)
             Re: Other things to consider: - (broomberg) - (6)
                 Interbase "seen" as going away... - (admin) - (5)
                     Re: Interbase "seen" as going away... - (broomberg)
                     PostGreSQL setup/complexity - (broomberg) - (3)
                         Yep. - (admin) - (2)
                             Re: Yep. - (broomberg) - (1)
                                 Shouldn't need one right away. - (admin)
             Wierd create index behaviour - (broomberg) - (6)
                 index create - (boxley) - (5)
                     Re: index create - (broomberg) - (4)
                         Well, Sybase still has some money - (tonytib)
                         Re: index create - (broomberg) - (2)
                             1.5 hours to create index - (broomberg)
                             That's why I'd second the Interbase recommendation - (tseliot)
         Re: MySQL vs Oracle question - (wharris2) - (2)
             Readonly - (broomberg) - (1)
                 Readonly? Hell, then, full speed ahead! -NT - (wharris2)
         14 hours later, still indexing - (broomberg) - (2)
             20 hours later, still indexing - (broomberg) - (1)
                 Wheeee - Done!!! - (broomberg)
         New design - (broomberg) - (1)
             Happy Ending! - (Meerkat)

Keep a mild groove on.
94 ms