Thread: Client.java size does not lagg your server.

Originally Posted by Boomer

That statement is false, it depends what makes your client class large. If you have a 1MB process void then that would slow down the server.

That statement is also false. Depending on what the method actually does, a huge method could easily process within a millisecond.

I seriously want to flame every single one of you right now about how retarded your posts are. But instead I will take the time out of my priceless day to explain to you kind people of rune-server, what really makes process times slow.

First of all, jagex hosts 2 worlds per computer, they don't have near 10GB of ram, because they are not retarded morons and they don't write useless and heavy-weight scripts that will hog lots of memory. One server(computer) that jagex uses to host two worlds, maybe has about 4-6GB of ram, (I believe jagex uses redhat linux for hosting), you guys know nothing about the difference between RAM and CPU, RAM can easily be increased by creating a PAGE on your harddrives, a PAGE is a block of memory stored on your harddrive that acts like it was RAM. I have 4 harddrives, and i CAN have each one store it's own PAGE block. If I did, I would have like 21GB of ram, but sinces Windows XP only handles like 3GB of ram, all I need is the hardram (sticks on my motherboard) because I have 2.37GB of hardram. If I wanted to, I could switch OS's and have 21GB of ram, but it's not needed and wont speed anything up.

The real thing is CPU, the more GigaHertz(GHz) the faster threads will be processed. So honestly jagex has around 4-6GB of ram, and atleast 5.0GHz. Reason why jagex can handle 4096 connections on one computer, is not only because of the computers specs (RAM+CPU), but because jagex pays a shit load (ruffly guessing about $10,000++ a month for the internet), because they have Telnet Coms, internet, if you wish go check a speed test for Telnet Coms. Thus, making all the input/output events transfer so fast that if you were to go as fast as the data being transfered, you would be ripped apart into a million tiny bits.

You people don't think that download speed matters when it comes to hosting a server? Sorry you're as wrong as obama when he said "yes we can". Download speed matters just as much as upload speed, if your download speed is bad, that means when a client sends data to the server(you), it will go slow, thus making operations slow and shitty. Honestly network speed matters more than RAM. Also, I want to just through in here, you know why 2speced has to have like 20GB of ram? Because it's a shitty written server and he needs that much memory to handle 500 players.

Now on to what causes heavy use of memory. Buffers in blocking i/o are filled, but are not sized correctly, each client class creates a static buffer for all input and output, usually like 50MB in size. Thats why when making a client/server program, to have it ensure the the capacity is only what it needs and resize when its ready to be downsized or upsized(dynamic buffer).
You guys think thread-per-client is bad? Not at all, it's just only bad in winterlove because it was done WRONG. The more threads the better, but if you use it wrong, things will only get worse. Thread pooling is the best to handle thread-tasks that will only be alive for a short amount of time, such as i/o events and player updating every 600ms.
And of course, the retarded processing winterlove uses, I will not explain this because pretty much everyone knows.

Originally Posted by Ultimate

Guys! Guys! Guys! What really causes lag are:

(1) IO Processes, e.g - loading and saving constantly
(2) Process timers
(3) Large arrays e.g. int[] array = new int[999999999];
(4) The player updating process
(5) Not using the garbage collector at intervals/ after loading processes
L

two is not true, to an extent. three is not true and 5 is not true

Originally Posted by Nicole

The 40gb Ram is incorrect, They use maybe 15gb, Because remember, They have PRO Coders, Not simple java, Also they have way better ways of doing it, because they created it first.

I know, 40 is an exaggeration. 12+

Originally Posted by Luke132

BattleScape 317's client.java was 1.3mb, and there are numerous servers with one over 1mb.

Point being?

Originally Posted by Realm

To put it simply, the performance of a program depends on (talking software-level) the amount and size of processes, and also the amount and size of threads.

As long you don't change the runtime of a class, adding even a million methods to it won't change the performance.

Exactly!

Originally Posted by Gnarly

I seriously want to flame every single one of you right now about how retarded your posts are. But instead I will take the time out of my priceless day to explain to you kind people of rune-server, what really makes process times slow.

First of all, jagex hosts 2 worlds per computer, they don't have near 10GB of ram, because they are not retarded morons and they don't write useless and heavy-weight scripts that will hog lots of memory. One server(computer) that jagex uses to host two worlds, maybe has about 4-6GB of ram, (I believe jagex uses redhat linux for hosting), you guys know nothing about the difference between RAM and CPU, RAM can easily be increased by creating a PAGE on your harddrives, a PAGE is a block of memory stored on your harddrive that acts like it was RAM. I have 4 harddrives, and i CAN have each one store it's own PAGE block. If I did, I would have like 21GB of ram, but sinces Windows XP only handles like 3GB of ram, all I need is the hardram (sticks on my motherboard) because I have 2.37GB of hardram. If I wanted to, I could switch OS's and have 21GB of ram, but it's not needed and wont speed anything up.

The real thing is CPU, the more GigaHertz(GHz) the faster threads will be processed. So honestly jagex has around 4-6GB of ram, and atleast 5.0GHz. Reason why jagex can handle 4096 connections on one computer, is not only because of the computers specs (RAM+CPU), but because jagex pays a shit load (ruffly guessing about $10,000++ a month for the internet), because they have Telnet Coms, internet, if you wish go check a speed test for Telnet Coms. Thus, making all the input/output events transfer so fast that if you were to go as fast as the data being transfered, you would be ripped apart into a million tiny bits.

You people don't think that download speed matters when it comes to hosting a server? Sorry you're as wrong as obama when he said "yes we can". Download speed matters just as much as upload speed, if your download speed is bad, that means when a client sends data to the server(you), it will go slow, thus making operations slow and shitty. Honestly network speed matters more than RAM. Also, I want to just through in here, you know why 2speced has to have like 20GB of ram? Because it's a shitty written server and he needs that much memory to handle 500 players.

Now on to what causes heavy use of memory. Buffers in blocking i/o are filled, but are not sized correctly, each client class creates a static buffer for all input and output, usually like 50MB in size. Thats why when making a client/server program, to have it ensure the the capacity is only what it needs and resize when its ready to be downsized or upsized(dynamic buffer).
You guys think thread-per-client is bad? Not at all, it's just only bad in winterlove because it was done WRONG. The more threads the better, but if you use it wrong, things will only get worse. Thread pooling is the best to handle thread-tasks that will only be alive for a short amount of time, such as i/o events and player updating every 600ms.
And of course, the retarded processing winterlove uses, I will not explain this because pretty much everyone knows.

Wow dude.
1. a page file is to slow for a server. You might as well just write client.java out as a text file and load everything from it if your going to use a page. RAM is not expensive, as i've said before. I just bought 8GB DDR2 for 92$.

2. 5.0GHz CPU? I doubt it because of the cooling cocts, but i could be wrong. Most servers have multiple slower CPU's.

3.

Sorry you're as wrong as obama when he said "yes we can".

Obama sucks, yes.

4.

You guys think thread-per-client is bad? Not at all, it's just only bad in winterlove because it was done WRONG.

I've been trying to explain that to the NIO freaks for months.