> By default it should continue to do what it does > right now. As a user if I can change some > configuration that makes Solaris follow the file i/o > pattern (insecure but quick) as Linux, it will > improve my productivity.
One has to wonder about productivity improvement if the system experiences a problem like a power loss and one loses, say, five hours worth of work and ends up with a system rebuild on one's hands. > Right now I am running a J2EE application and it does > quite a bit of File i/o and hence my application runs > a bit slower on Solaris x86. My knowledge about Unix > internals is very limited but as a user I would love > to see my Solaris x86 box beat Linux to complete the > same task. I am not questioning the validity of > current design. Well, perhaps improving the application would be an option. If I were you, I'd start studying DTrace [docs.sun.com], and see if I could pinpoint the bottlenecks. Perhaps your problem may be entirely solvable without compromising data integrity design of Solaris. > > Do you value your data? > > Not always. Say on my Java development machine > running Solaris x86, I am ok if there is a remote > chance that my data is corrupt. > I would not like the same risk on a machines running > my business critical databases. What about your customers running your application? This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
