spencer@dssmv0.mpr.ca ( Reid Spencer) (04/10/90)
I'm involved in a T1 network management project that requires the use of an RDBMS (Ingres) to provide customers with extensive access to the network information. However, INGRES is too slow for us to be updating for a real-time network management system. To improve performance, we're investigating the use of an OODBMS or a persistent storage system for C++. We have investigated Ontologic's Ontos product and the "E" language. So far, neither of these seem suitable for our purposes. Has anyone out there written a simple, cheap, robust persistent storage mechanism for C++? We would like to avoid solutions that have the following characteristics: 1) Doesn't support multiple inheritance. 2) Users non-standard version of C++ language (i.e we don't want to back ourselves into a corner using a product that modifies the language in any way). 3) Doesn't support crash/failure recovery 4) Requires extensive programming support on a per class basis. 5) Can't perform at least 100 object transactions per second (preferably, we'd like something that can perform at or near the 1000 object transactions per second level). Target is a SUN 3 or DEC MicroVAX. General questions: 1) Does an efficient persistent storage necessarily require changes to cfront? If so, are such changes planned? 2) How "dangerous" is pointer swizzling as implemented in "E"? Can such mechanisms be implemented in hardware (similar to some MMU mechanisms today)? Has this already been done? Pardon my ignorance if such a system has already been posted to this news group. _______________________________________________________________________________ Reid Spencer Software Engineer Voice: (604) 293-5334 Microtel Pacific Research, Ltd. Fax: (604) 293-5787 8999 Nelson Way, Burnaby, BC Internet: spencer@egypt.mpr.ca Canada V5A 4B5 UUCP: uw-beaver!ubc-cs!eric!egypt!spencer "On a clear disk, you can seek forever"