Richard Troy wrote:
My point here is that "out of the box," I don't think Ingres the company ever really tried to size things appropriately and Ingres the product suffers for it with people like you getting frustrated. ...It's a sophisticated product and there's a lot to learn. Picking it all up right away can be frustrating. And the cost of training might seem daunting for a supposedly free database product. But I can assure you that properly configured, Ingres is almost certainly the best scaling, best performing relational database system in existence today - if anything does beat it, it won't be by much and it would be for a rare boundary condition case. Finally, if you have over a gig of main memory, consider giving the DMF cache at least a quarter, or perhaps a third of it. The transaction logfile is "circular", so size it fairly large also. These are general recommendations and not particularly targeted at your specific problem...
Hi Richard, thanks for your answer. Indeed, I'm not a Ingres newbie and I have installed quite a lot of Ingres servers and I'm quite familiar with Ingres configuration tools. BTW, I'm not frustrated at all with Ingres. I like it very much. I just have a particular problem with Ingres 2006 compared with Ingres R3 3.0.3 which is surprising as Ingres 2006 is not much more than a re-branded Ingres R3 with some fixes. Problem: all Windows-based Ingres 2006 servers have a severe performance problem when reloading databases (taking about 6 times as long as R3). I have this problem with highly customized machines as well as with out-of-the-box-machines. I only did this out-of-the-box setup because Ingres tech support supposed I have a weird setup and recommended to test again with default settings. I deeply believe that Ingres 2006 has a bug that was not there in R3. Regards Gerhard _______________________________________________ Users mailing list [email protected] http://lists.ingres.com/mailman/listinfo/users
