Rhett, I am sorry man, I didn't mean it that way. In fact automatic tracking of memory hogs would be very interesting for us, I could use it right now on our own production site.
Please feel free to contribute, we need more guys like you, I am sorry for making fun of the idea, as I said it was probably right for the problem you were trying to solve. PLgC marcf > -----Original Message----- > From: Rhett Aultman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 11, 2002 12:41 PM > To: [EMAIL PROTECTED] > Subject: PRIVATE:(RE: [JBoss-dev] Implementing a Resource > Protection System?) > > > Marc, > > I really do admire you, and as such I know about your brutal > honesty and sharp sense of humor, but am I really deserving > of that kind of treatment? This wasn't for a hosted > environment for tracking inadvertant hogs. It was for an > environment of scheduled jobs being written by me and > everyone on my team that were simple but intense and that > were tested before being left in the scheduled environment > (personally, I didn't even want to write the damn thing...but > people around here have never heard of cron and won't accpet > a non-Java answer anyway). The only purpose was to alert > jobs that they needed to lighten the load or the heap would > run out. It was necessary because team members were writing > jobs of heavy memory utilization that would sometimes be > running concurrently with other memory intensive jobs. Yes, > it worked there, and it worked because the people developing > jobs for it knew that if one of their jobs used up the heap > and didn't complete, their heads would roll the next day. > Yes, it would be retarded in a hosted environment trying to > spot hogs. No, I am not that stupid. I may not be you or > Dain or Juha or any of the other crowd, but I am not stupid. > I may be all of 22, fresh out of college, and only now > teaching myself about OS kernel development, but I still am > not stupid. > > What I was attempting to do was to explain to the original > author all the further I'd been able to get on such an issue, > which was to spot when memory's getting seriously tight. As > of now, I still don't see a way to get anything more > fine-grained than that, and I really don't see any APIs out > there for doing it "inside the VM" (though the JNI option is > interesting). I know I'm not a JBoss contributor, nor am I > Marc Fleury, but I thought that, at the time, I might have > had something meaningful to add by pointing out the > shortcomings of what appears to be readily available right > now and by pointing out all the further that I can see > someone getting with those tools, which clearly isn't far enough. > > I believe in JBoss. I use JBoss. I stand behind JBoss. I > even do what I can do to try and make JBoss better (although > I'm often out of my league and in the presence of those who > have far more expertise and experience than me). If my input > is really that unwelcome, just say so, and you won't have to > be subjected to my commentary any further > > -----Original Message----- > From: marc fleury [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 11, 2002 12:07 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Implementing a Resource Protection System? > > > > I've thought about doing this in some of the other > > architectures I've written from time to time. It's possible > > to keep an eye on memory usage and track its stats over time, > > so you can know when memory's becoming scarce and start > > telling different parts of the system "Memory's tight. Can > > you do what you can do to lighten the load?" That wasn't all > > that hard to do- every time this architecture deployed a > > "job" to run, it kept a handle to them and would > > asynchronously call a method on them that contained "best > > effort" code to lighten up the load and call the GC. That > > works fine when you just know that you're using more and more > > memory and just want to politely ask deployed code to attempt > > to help out. > > Rhet, > > LOL, do you realize how dumb this is??? You are saying that > in the hosted environment, when one module is a hog, the > system asks "politely" for the other well behaved parts, to > "please let go of some memory, cause the hog over there wants > some"... Dude, you were sleeping when you wrote this. I'll > sue you if you commit this to our tree :) > > Marcf > > PS: for your own application it was probably fine > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > PC Mods, Computing goodies, cases & more > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek PC Mods, Computing goodies, cases & more http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
