Well think about that: in that world, no need to rescue wallstreet so that they can come back and fuck everyone in the world (yes, not just everyone in america but everyone IN THE WORLD) again.
Lets return to the earth, have half of us killed, and go back to hunting venison like we very well used to before some assholes started to chat about this "civilization" crap we are in right now.
Fuck that.
Back to the trees people, this stupid "modern society" thing didnt work.
Interesting (and correct) distinction between paging and process swaping.
There is, however, an important corelation: buffers and read caches take ram, ram is needed by proceses, proceses get swaped out (and that generally fucks them up if they are interactive or snappy, like an httpd).
Its good that you pointed this out, because what Ive seen with my own eyes, is precisely that: very intensive I/O with large writes can be very aggressive towards your RAM and cause swaping elsewere (ive seen it... you can tune many parameters to get ahold of the beast), but i guarantee it: if you have a 64GB key sort cache on your DB, youll need a ridiculously large box to get the whole thing to work decently (say, 128GB RAM?), or a very good and fast SAN or local storage device that can help you out in your memory shortage (which, for those sizes, its always gonna be short).
As you can see, the logic still applies: in some of those cases, your only way out will be to aggressively use swap. On other cases, you may tame as the provider recomends: if oracle tells you to use their mem page manager (no idea, im just inventing here) to configure it for the resources you have, you go ahead and do that. But there are other apps that will expect you to come up with a livable environment.
Well... when they get big, the queries just plain wont fit in your RAM. This is true for any DB that gets big enough to not be able to fit the whole thing in ram.
Since in a DW you want users to be able to browse, but seldom in realtime data (you generally process and insert into the dwh asyncronously, not on-demand from end users). In those cases, using a good very fast swap device may be the ONLY choice to actually finish your processing
Is that transactional servers that swap are useless.
There, ive said it (more than once and ive heard it from the mouths of real unix gawds): swap is not usable in a heavy production environment webserver, mailserver, printserver or whatever thingie that does syncronous jobs (need to provide an answer in seconds or minutes after a request comes).
OLAP Database servers are also in this category: if youre swaping, it aint workin.
There are only a few applications that actually benefit from swapping (large datawarehouses come to mind), but they almost do the part of their job that consumes more memory in an asyncronous way.
Bottom line: set your swap to whichever reasonable figure you can calculate from a realistic-as-possible memory usage scenario for the particular application you are using.
One might argue that pure capitalism does account for the extra costs, but that the value that we as a colective give to many of the intangible or costs-to-the-earth is sequestered by what we sadly call "public opinion" which is mainly paid for by private hands that pretty much live nice lives by fucking up the planet for the rest of us.
All in all, we need to kick the asses of stupid senseless politicians to show them that its WE (the market) who gives value to things, not them and by decree.
When the court decides its legal to rip the dvd's, but only with spyware that hinders your boxen and shows you naked celeb-titties and is well branded by a reputable name like real networks.
You got it all wrong: redhat does not limit at all what you CAN do with their thingie, its the legal agreement what makes the difference: you can bypass registration and installation key with one click
And, BTW, why is it a pita to integrate? Ive had it within an ADS, then as a substitute for ADS, then as a dropin exchange replacement, then as a plain unix-based mailserver for unix clients....
Ive had it working for like five enterprises here, some of 5k accounts, some smaller.
It syncs my iphone vÃa push, it syncs all the wince and winme devices weve thrown at it, if youve a BES (eek, talk about shitty messaging), it works fine with it.
If you mean Outlook plain support.... then okay, it is quircki on that end. But the problem with that is OUTLOOK. Not zimbra!
The ZWC works perfectly and install easyer than most sw ive seen.
Slashdot Mirror
I know i know, lets give it to some wallstreet bankers!
Its the space, silly.
How on earth is apple able to cram 16 gigs in an iphone, while the newest tmobile thingie can store, what, up to a gb?
Thats the driving force behind jobs: some strange space cramming genius (or exclusive patent license).
They do that a lot.
I know.
Finally... someone got it.
Jeeze.
Thats why i advocate masturbation.
I bow in signal of respect.
Well think about that: in that world, no need to rescue wallstreet so that they can come back and fuck everyone in the world (yes, not just everyone in america but everyone IN THE WORLD) again.
And, by the way, its people like you that make me feel grateful for Sarah Palin.
And i dont hate civilization. Im just pointing out that it doesnt work as it should. And it doesnt.
Have you ever heard about "you can solve everything through love" philosophy?
I have.
I call it a lie.
I wanna see it flip and take it all with it.
Lets return to the earth, have half of us killed, and go back to hunting venison like we very well used to before some assholes started to chat about this "civilization" crap we are in right now.
Fuck that.
Back to the trees people, this stupid "modern society" thing didnt work.
I want to be a synergistic procesing element!
Doesnt everyone?
nai
Interesting (and correct) distinction between paging and process swaping.
There is, however, an important corelation: buffers and read caches take ram, ram is needed by proceses, proceses get swaped out (and that generally fucks them up if they are interactive or snappy, like an httpd).
Its good that you pointed this out, because what Ive seen with my own eyes, is precisely that: very intensive I/O with large writes can be very aggressive towards your RAM and cause swaping elsewere (ive seen it... you can tune many parameters to get ahold of the beast), but i guarantee it: if you have a 64GB key sort cache on your DB, youll need a ridiculously large box to get the whole thing to work decently (say, 128GB RAM?), or a very good and fast SAN or local storage device that can help you out in your memory shortage (which, for those sizes, its always gonna be short).
As you can see, the logic still applies: in some of those cases, your only way out will be to aggressively use swap. On other cases, you may tame as the provider recomends: if oracle tells you to use their mem page manager (no idea, im just inventing here) to configure it for the resources you have, you go ahead and do that. But there are other apps that will expect you to come up with a livable environment.
We call this pam_limit here in penguin land. We hail he daemon too. Greetings.
Well... when they get big, the queries just plain wont fit in your RAM. This is true for any DB that gets big enough to not be able to fit the whole thing in ram.
Since in a DW you want users to be able to browse, but seldom in realtime data (you generally process and insert into the dwh asyncronously, not on-demand from end users). In those cases, using a good very fast swap device may be the ONLY choice to actually finish your processing
Its a conspiracy!!
Is that transactional servers that swap are useless.
There, ive said it (more than once and ive heard it from the mouths of real unix gawds): swap is not usable in a heavy production environment webserver, mailserver, printserver or whatever thingie that does syncronous jobs (need to provide an answer in seconds or minutes after a request comes).
OLAP Database servers are also in this category: if youre swaping, it aint workin.
There are only a few applications that actually benefit from swapping (large datawarehouses come to mind), but they almost do the part of their job that consumes more memory in an asyncronous way.
Bottom line: set your swap to whichever reasonable figure you can calculate from a realistic-as-possible memory usage scenario for the particular application you are using.
One might argue that pure capitalism does account for the extra costs, but that the value that we as a colective give to many of the intangible or costs-to-the-earth is sequestered by what we sadly call "public opinion" which is mainly paid for by private hands that pretty much live nice lives by fucking up the planet for the rest of us.
All in all, we need to kick the asses of stupid senseless politicians to show them that its WE (the market) who gives value to things, not them and by decree.
Shiit...
This makes napalm look like a kiddie rubber slingshot.
They could also become the Russia of methane!!
Evil, evil empires i tell ya.
When the court decides its legal to rip the dvd's, but only with spyware that hinders your boxen and shows you naked celeb-titties and is well branded by a reputable name like real networks.
None of that commie-hippie linux-shit, no sireee.
Get a grip, hippo, they dont mean your kb.ms thingie. They mean the INTEROPERABILITY docs, which you will NEVER see in a website such as your msdn.
You got it all wrong: redhat does not limit at all what you CAN do with their thingie, its the legal agreement what makes the difference: you can bypass registration and installation key with one click
And, BTW, why is it a pita to integrate? Ive had it within an ADS, then as a substitute for ADS, then as a dropin exchange replacement, then as a plain unix-based mailserver for unix clients....
I just didnt suffer with it at all.
Love the damned thing
Get off the pipe, my friend.
Ive had it working for like five enterprises here, some of 5k accounts, some smaller.
It syncs my iphone vÃa push, it syncs all the wince and winme devices weve thrown at it, if youve a BES (eek, talk about shitty messaging), it works fine with it.
If you mean Outlook plain support.... then okay, it is quircki on that end. But the problem with that is OUTLOOK. Not zimbra!
The ZWC works perfectly and install easyer than most sw ive seen.