Re: JVM/Java memory footprint

In article <1170388184.408678.181470@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "Daniel
Pitts" <googlegroupie@xxxxxxxxxxxxx> wrote:
On Feb 1, 5:22 pm, nukl...@xxxxxxxxxxxx (nukleus) wrote:
In article <45c221d6$0$764$5a6ae...@xxxxxxxxxxxxxxxxx>, Alex Hunsley

<red...@xxxxxxxxxxxxxx> wrote:
nukleus wrote:
[snip lots of rant]

Lots of stamp?

If you don't like the help here, you could demand back the money you
paid for it...

I DEMAND IT!!!!!

[snip more rant]

Yep, considering that your sense of humor
is on the par with my fridge, what else
would I expect you to leave in the post?

What are you foaming at the mouth about,
mr. smart?

What's the word I'm looking for?
Oh yeah, *plonk*

EXACTLY. Just like just about all of those
high priests eventually do.

You see, for some strange reason, it is not
enough for you to simply set your filters
and be done with it.

Nope. You have to come here and announce
to the whole world what an intolerant
blood boiling idiot you are, while, at the same
time, thinking it makes you "superior",
just by the mere fact that you announced
your foolish "plonk" thing. Do you realize
how much do I care about your "plonks"?

And the most amazing thing about this
is that you are also perverts, inevitably so,
because most of you, if not all, simply
use this stupid template of announcing your
plonk, but in actuality, you are still reading
those, you claim to have plonked, and I
have seen PLENTY of those cases. And it goes
as far, as once in a while, you even follow
up on the their posts. Because you could be
made to dance to just about any tune there is,
and, eventually, can not contain hiding in the back
and pretending you are not seeing it all.
Once you are tickled enough, you will appear
out of nowhere. See?

Because, first of all, by plonking me, YOU
are at a disadvantage, cause I can read your
posts if I want to, but you can not read mine.
So, from now on, no matter how much fun I can
have with you, showing your great achievements,
and laughing my rears of at you, you wont be able
to even know that you might have become
but a laughing stock.

See?

I do not have, never had, and have no plans
to "plonk" anyone, even the most outrageous idiots,
cause I know how to use my "next" button. And quite
often, those I should have "plonked", turn out to
be the about the finniest posts one can find.

Btw, what is the Subject header of this thread?
Why are you posting all this stuff being UTTERLY
off topic?

Are you a troll?

This is a technical group and you claim to have
more than but a few broken neurons on line.
Can't you figure out the simpliest thing of this grade?

Or you, "experts" around here, think this group
BELONGS to you and YOU are here to do whatever YOU
please, regardless of your own netti-quetti-betti-fetti,
you yourselves claim to follow, or equivalent thereof
with all your "thou shalt not do this, and thou shalt not
do that" stuff?

THOU SHALT NOT POST OFF TOPIC IN A TECHNICAL GROUP.

THOU SHALT NOT FOLLOW THE POSTS OF THOSE,
THEY CONSIDER TO BE OF INFERIOR RACE OR CREED.

THOU SHALT NOT ENGAGE IN INSULTS AND REDICULE
OF THOSE WHO DO HAVE A VALID POINT.

You want more?

Or shell I let you talk to my monkey?

Now, back to the topic of this thread:

What i found out is that in order for you to
run a simple program, which only does things like

int foo = 1,

what would all your super-advanced technoly
of delayed just about everything do?

Well, if you set a brake point on main(),
and then start up your app, you may be unpleasantly
surprised, that before your breakpoint is hit,
some heavy duty time has to elapse, and that is just
about the first thing i have noticed when i tried
to run the code i interited. For some strange reason,
it would take it a long time to evan come up.
When I looked at processes and resources,
i was not so pleasantly surprized to see that by
the time I select my first choice from the menu,
before actually doing anything, it swallowed
about 20 megs. For what?

Well, it turns out that before you main() gets hit,
you, royal architects, have to load the entire
bloatware, called JVM.

And even though that simpliest program that does not
even do anything consists of a single CPU instruction,
taking 1 clock cycle, for some strange reason, you
have to load the whole universe.

For what?

Well, because it is called JVM.
Bloatware that is.
It can't use the same concepts that are used
in virtual memory management, called page fault
and bring up only those things, it actually needs
this very moment, it seems.

True, I haven't investigated this issue to the end,
and I hardly need to, because I see the run time
results without even figuring out why is it so
bloated.

And I bet you, if you run several java apps,
you'd be loading the same JVM again and again,
despite the fact that they can't even talk to
each other without going outside the scope
of JVM itself.

So...

What is this great breakthru are we talking about here,
if you don't seem to manage even thouse things that
were resolved generations ago?

I was quite surprised that the AWT wasn't even
thread safe and if you want to use threads,
you'd better download 50+ megs of the latest
version of the bloatware, and not only you,
but ALL your customers and co-developers.

How could THAT be?

Are you joking or something?

So, for the real world applications, especially
those, we are talking on this specific thread,
you have to load literally gigabytes of JVM
alone, one for each instance of your app.

So, if you are writing apps for the biggest and
baddest of themn all, and ESPECIALLY in network
related areas, which Java claimed to be designed
for on the first place, you better tell your boss
that you need to order the latest version of
the mainframe with super cooled CPU and create
a huge service room just to keep all the cooling
equipment in.

You'd have to learn how to walk on your ears
if you want to be involved in anything big
related to java.

So, if he, for some strange reason, thinks that
they just want to push a few buttons and update
the global system of whatever they deal with,
YOU are in trouble. Because he'll probably think
that it is YOU that is the problem and not that
bloatware they have chosen to step into.

Good enough for "on-topic" material?

Your turn, oh masters of dizastas.

Cause it looks like we're going to have some fun here.

.