The math I wrote is wrong. Skype is half a meg per minute, giving you 2000 minutes in theory. So you could actually save a bit of money provided you don't talk too much; but still we wouldn't care, you are paying us for the data traffic and we still make money on your inbound minutes since Skype can't take the phonenumber, granted you aren't the one paying us, we still carry your traffic and make money on you.
Knock yourself out if you want to Skype on our system. Data traffic is "free" for the first GB if you pay a monthly fee of about $30, that gives you about 1000/30 = 330 minutes of talk for $30 (or the same as you are paying for GSM to GSM in our system anyways - so you'd lose money if you don't max out your data usage). After the 330 minutes are up you are paying $1 per MB or in other words 50 cents on the minute. What you then have to remember is the system isn't designed to QoS your Skype, so not only are you paying more, you will have higher rate of dropped calls - but hey, whatever floats your boat.
Oh and before you think of something smart like Skype when roaming, data tarif can be as high as $15/MB.
In short, if you want to fleece yourself, carriers are not going to complain.//Only in one case would it make sense, when calling from your mobile to some foreign country, but still we wouldn't care. We don't make anything on those calls anyways (thanks to EU and their messing in the affairs of carriers).
WoW (and other MMOs) needs torrents, because they have an very high to extremely high burst ratio. When a new patch is deployed for Linux it needs to propagate out to various distributions, people need to start packing it and then end users auto update will pick it up eventually. This means it's often distributed over time. When WoW deploys a new patch, they have 10 million people trying to get it at once in order to be first in new instances. Even the big distributors have trouble coping with this - and over a short period of time the need for bandwith will drop to very low levels as people are getting up-to-date, so there is no financial incentive for Blizzard to invest in the hardware to cope with deployment.
They aren't talking about physical CPUs, they are talking about cores within any given CPU, which I doubt you where having 64 of. While this may seem like a moot point, when scheduling it is very important to keep track of what's going where since you are usually at least sharing L3 cache on a single die.
With 5 years of backlog you are usually beyond the point where it matters - I have that with my bank (not in US), I have a few times needed to get proof of a payment several years back, but never needed to go beyond 5 years.
Do you actually read what people write or do you just settle on a viewpoint and stick with that regardless of how stupid you might seem?
Let me cut this out so you understand it, I'm averaging 37 million transactions a day on 2 servers with a total of 8 cores and 8 GB ram and 8 harddrives, we expect to be able to cope with some 4-500 million transactions a day on this hardware. When we need to upgrade it will be the hard drives that goes first, change to a 10GBit SAN with 2-3 shelves of drives and the sky is the limit, when we need more CPU's we can enable the other 4 cores in both servers (need license for that) - when RAM is the issue we can go all the way to 64GB.
Handling 2000 users with one commit per second per user is a walk in the park.
Now for your programming statement, yes it is what people do, but that doesn't mean it's a preferred way, it is what uneducated people does - and trust me, you really don't want to hope for a guy like me to come save your arse after you are done screwing with the database, we are expensive and doing it the right way around from the get go will save your company and your own arse.
And for the love of god, don't think you know anything about MMORPG's then. Having people lose a minute with thousands of people online will mean someone just got cheated of his yber item. Take the lich king for instance in WoW, this is a fight that will wipe your average guild 95 out of 100 times, if you get him, you get a title that is hands down the most sought after. Should you happen to lose a minute of transactions where a guild just took down the LK, you got 10 or 25 extremely pissed of people, this is a deal breaker for most gamers - I sure as hell would stop playing if I got cheated out of that. If you make a habbit of losing a minute every once in a while you are dead in the water.
In fact, it is a very limited set of applications where you don't mind losing some data, most situations data is the single most valuable asset in a company, you should probably change your view and the way you handle data, sounds like you are a disaster waiting to happen.
*Ahrem* I'm averaging around 37 million transactions a day, the system is almost in idle state (2 servers with 4 cores, 4 GB ram, 4 hard drives in a hot standby with real-time replication - very very cheap and simple setup), we expect to cope with 20-30 times more users on our system. It's build for reliability and speed (HA and HP).
Synchronizing over the database might be what most idiots do (and they have done it here), but it is by no means a preferred way of doing it - it's what happens when you got people with lack of threading and/or clustering experience programming.
And you have obviously never played an MMORPG other than maybe casual, there is nothing in the world of MMORPG gamers that is allowed to be lost. Turbine once dropped a whole day of transactions due to faulty SAN on their DDO servers, trust me, they lost a lot of money on that.
SMS is using the signalling service within the GSM network, this is a very limited technology and can't easily be upgraded, thus you pay way more than for the technology where you can offload to a separate link.
We aren't using triggers for your readability, your maintenance or your speed, we are using triggers and constraints to ensure our dataset is correct.
OP was bashing the programmers for always committing to hard drive, what was supposed to go there - and is going there in most MMOs - to me it sounded like the hardware setup was their downfall.
OP was wrong when he said traversing a CPU takes more than 5 cm, but he is still right, light speed is becoming a significant problem - also, note the core clock speed of your CPU is a very very tiny extremely limited area - everything else is going at bus speed (usually somewhere between 200Mhz and 2Ghz).
And I don't know them nordichardware guys, but I do know some math and physics, at 7Ghz light is only travelling 4,2 cm per clock cycle under optimal conditions - this is well within theoretical limits, but you are approaching the upper limits fast.
Speed of light is a very physical barrier, everything else within our solar system is travelling below this speed - that means, if light can only go 4-7 cm in a given clock cycle, your wee little electrons aren't going to go faster than that.
Rest of your comment flat out doesn't make sense, so I fear you aren't kidding...
As far as I know, most of Europe has free speech, but you are accountable for what you say - and I'm pretty sure it isn't much different in the US, I bet that if you walk up to an officer of the law in the US and tell him you have a bomb and will detonate it, you are in for a good spanking.
Ebola Zaire is way too agressive for a total wipeout. Within 1 week of first infection everything would be shut down and within 2-3 weeks more it would have killed off itself (a long with millions of people).
The perfect killer is something like the spanish flu, high incubation time, looks like normal flu (as you suggested, people go to work/supermarket) and then drop dead.
Errr, most companies sell you close to advertised, a lot of companies down right cheat.
Examples: A crate of tomatoes advertised to 600g - do you seriously expect them to hit 600g with 5 tomatoes each time? Bacon, ham - and often meat in general - is pumpes so full of water you will often end up losing some 7-10% Newspapers claim to do investigation while they often verbatim copy. Cars claimed to do umpteen miles per gallon (the car I got does 22 km/l according to specs, usually won't go above 18)
Yeah that makes a whole lot of sense, my mobile phone is covered by at least 100 patents, if not 1000, how would anyone ever make a profit with that kind of licensing?
No, actually each drive comes with a build in cat, gerbil and a baloon, when the drive is powered down the cages to each animal are opened and the cat chasing the gerbill in the closed area will generate enough static electricity rubbing against the baloon to wipe the key.
Pure and simple, no fancy faulty capacitor to ruin your day.
The math I wrote is wrong. Skype is half a meg per minute, giving you 2000 minutes in theory. So you could actually save a bit of money provided you don't talk too much; but still we wouldn't care, you are paying us for the data traffic and we still make money on your inbound minutes since Skype can't take the phonenumber, granted you aren't the one paying us, we still carry your traffic and make money on you.
You are kidding right?
Knock yourself out if you want to Skype on our system. Data traffic is "free" for the first GB if you pay a monthly fee of about $30, that gives you about 1000/30 = 330 minutes of talk for $30 (or the same as you are paying for GSM to GSM in our system anyways - so you'd lose money if you don't max out your data usage). After the 330 minutes are up you are paying $1 per MB or in other words 50 cents on the minute. What you then have to remember is the system isn't designed to QoS your Skype, so not only are you paying more, you will have higher rate of dropped calls - but hey, whatever floats your boat.
Oh and before you think of something smart like Skype when roaming, data tarif can be as high as $15/MB.
In short, if you want to fleece yourself, carriers are not going to complain. //Only in one case would it make sense, when calling from your mobile to some foreign country, but still we wouldn't care. We don't make anything on those calls anyways (thanks to EU and their messing in the affairs of carriers).
They tried it in Basel (Switzerland), didn't work out too well for them.
This is spot on.
WoW (and other MMOs) needs torrents, because they have an very high to extremely high burst ratio. When a new patch is deployed for Linux it needs to propagate out to various distributions, people need to start packing it and then end users auto update will pick it up eventually. This means it's often distributed over time. When WoW deploys a new patch, they have 10 million people trying to get it at once in order to be first in new instances. Even the big distributors have trouble coping with this - and over a short period of time the need for bandwith will drop to very low levels as people are getting up-to-date, so there is no financial incentive for Blizzard to invest in the hardware to cope with deployment.
They aren't talking about physical CPUs, they are talking about cores within any given CPU, which I doubt you where having 64 of. While this may seem like a moot point, when scheduling it is very important to keep track of what's going where since you are usually at least sharing L3 cache on a single die.
With 5 years of backlog you are usually beyond the point where it matters - I have that with my bank (not in US), I have a few times needed to get proof of a payment several years back, but never needed to go beyond 5 years.
Do you actually read what people write or do you just settle on a viewpoint and stick with that regardless of how stupid you might seem?
Let me cut this out so you understand it, I'm averaging 37 million transactions a day on 2 servers with a total of 8 cores and 8 GB ram and 8 harddrives, we expect to be able to cope with some 4-500 million transactions a day on this hardware. When we need to upgrade it will be the hard drives that goes first, change to a 10GBit SAN with 2-3 shelves of drives and the sky is the limit, when we need more CPU's we can enable the other 4 cores in both servers (need license for that) - when RAM is the issue we can go all the way to 64GB.
Handling 2000 users with one commit per second per user is a walk in the park.
Now for your programming statement, yes it is what people do, but that doesn't mean it's a preferred way, it is what uneducated people does - and trust me, you really don't want to hope for a guy like me to come save your arse after you are done screwing with the database, we are expensive and doing it the right way around from the get go will save your company and your own arse.
And for the love of god, don't think you know anything about MMORPG's then. Having people lose a minute with thousands of people online will mean someone just got cheated of his yber item. Take the lich king for instance in WoW, this is a fight that will wipe your average guild 95 out of 100 times, if you get him, you get a title that is hands down the most sought after. Should you happen to lose a minute of transactions where a guild just took down the LK, you got 10 or 25 extremely pissed of people, this is a deal breaker for most gamers - I sure as hell would stop playing if I got cheated out of that. If you make a habbit of losing a minute every once in a while you are dead in the water.
In fact, it is a very limited set of applications where you don't mind losing some data, most situations data is the single most valuable asset in a company, you should probably change your view and the way you handle data, sounds like you are a disaster waiting to happen.
*Ahrem* I'm averaging around 37 million transactions a day, the system is almost in idle state (2 servers with 4 cores, 4 GB ram, 4 hard drives in a hot standby with real-time replication - very very cheap and simple setup), we expect to cope with 20-30 times more users on our system. It's build for reliability and speed (HA and HP).
Synchronizing over the database might be what most idiots do (and they have done it here), but it is by no means a preferred way of doing it - it's what happens when you got people with lack of threading and/or clustering experience programming.
And you have obviously never played an MMORPG other than maybe casual, there is nothing in the world of MMORPG gamers that is allowed to be lost. Turbine once dropped a whole day of transactions due to faulty SAN on their DDO servers, trust me, they lost a lot of money on that.
You can't compare those technologies.
SMS is using the signalling service within the GSM network, this is a very limited technology and can't easily be upgraded, thus you pay way more than for the technology where you can offload to a separate link.
We aren't using triggers for your readability, your maintenance or your speed, we are using triggers and constraints to ensure our dataset is correct.
OP was bashing the programmers for always committing to hard drive, what was supposed to go there - and is going there in most MMOs - to me it sounded like the hardware setup was their downfall.
Wouw, just... wouw.
Seek help.
"Your Googling May Vary."
Yes, that is exactly the problem with NoSQL.
OP was wrong when he said traversing a CPU takes more than 5 cm, but he is still right, light speed is becoming a significant problem - also, note the core clock speed of your CPU is a very very tiny extremely limited area - everything else is going at bus speed (usually somewhere between 200Mhz and 2Ghz).
And I don't know them nordichardware guys, but I do know some math and physics, at 7Ghz light is only travelling 4,2 cm per clock cycle under optimal conditions - this is well within theoretical limits, but you are approaching the upper limits fast.
You are kidding right?
Speed of light is a very physical barrier, everything else within our solar system is travelling below this speed - that means, if light can only go 4-7 cm in a given clock cycle, your wee little electrons aren't going to go faster than that.
Rest of your comment flat out doesn't make sense, so I fear you aren't kidding...
Was thinking, what's wrong with plain old gaffa?
As far as I know, most of Europe has free speech, but you are accountable for what you say - and I'm pretty sure it isn't much different in the US, I bet that if you walk up to an officer of the law in the US and tell him you have a bomb and will detonate it, you are in for a good spanking.
Ebola Zaire is way too agressive for a total wipeout. Within 1 week of first infection everything would be shut down and within 2-3 weeks more it would have killed off itself (a long with millions of people).
The perfect killer is something like the spanish flu, high incubation time, looks like normal flu (as you suggested, people go to work/supermarket) and then drop dead.
Fusion is easily done, the military figured that out ages ago. The problem is containing the nuke used to set off the fusion...
Errr, most companies sell you close to advertised, a lot of companies down right cheat.
Examples:
A crate of tomatoes advertised to 600g - do you seriously expect them to hit 600g with 5 tomatoes each time?
Bacon, ham - and often meat in general - is pumpes so full of water you will often end up losing some 7-10%
Newspapers claim to do investigation while they often verbatim copy.
Cars claimed to do umpteen miles per gallon (the car I got does 22 km/l according to specs, usually won't go above 18)
The list goes on...
10% of gross revenue?
Yeah that makes a whole lot of sense, my mobile phone is covered by at least 100 patents, if not 1000, how would anyone ever make a profit with that kind of licensing?
Really? And what happens the day you decide to move to another city? What if you have an shop online, where are the boundaries then?
Or just pick a safe word that is easy to remember.
Wait what? So my phone only has draw picture and I should stop using that because it's unsafe?
I'll take a little security over no security thank-you-very-much.
Well they do have two sharp points...
No, actually each drive comes with a build in cat, gerbil and a baloon, when the drive is powered down the cages to each animal are opened and the cat chasing the gerbill in the closed area will generate enough static electricity rubbing against the baloon to wipe the key.
Pure and simple, no fancy faulty capacitor to ruin your day.