Is this server strategy reckless and/or insane?
-
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
Are IOPS what you want for heavy duty users are making database writes concurrently all day long? I don't know much about drive characteristics/performance other than the basic throughput stuff. Because backup is streamed out in realtime that's taken care of as far as I'm concerned, part of what makes Raid 0 a candidate at least.
-
@creayt said in Is this server strategy reckless and/or insane?:
@dustinb3403 said in Is this server strategy reckless and/or insane?:
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
Are IOPS what you want for heavy duty users are making database writes concurrently all day long? I don't know much about drive characteristics/performance other than the basic throughput stuff. Because backup is streamed out in realtime that's taken care of as far as I'm concerned, part of what makes Raid 0 a candidate at least.
Yes IOPS are the consideration you need to be looking at. What has yet to be answered is how active is this database going to actually be?
Will you have 10,000 people/processes constantly making changes?
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
@creayt said in Is this server strategy reckless and/or insane?:
@dustinb3403 said in Is this server strategy reckless and/or insane?:
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
Are IOPS what you want for heavy duty users are making database writes concurrently all day long? I don't know much about drive characteristics/performance other than the basic throughput stuff. Because backup is streamed out in realtime that's taken care of as far as I'm concerned, part of what makes Raid 0 a candidate at least.
Yes IOPS are the consideration you need to be looking at. What has yet to be answered is how active is this database going to actually be?
Will you have 10,000 people/processes constantly making changes?
Ideally more than that, but it'll be a gradual climb. Right now it's in private alpha w/ ~ 100 users and they post stuff all the time. Once I make it public I imagine the content volume will skyrocket.
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
He's got backups of the data. He's doing devops style backups.
-
@creayt said in Is this server strategy reckless and/or insane?:
@dustinb3403 said in Is this server strategy reckless and/or insane?:
@creayt said in Is this server strategy reckless and/or insane?:
@dustinb3403 said in Is this server strategy reckless and/or insane?:
We all understand that there are differences with different RAID types.
The point of the matter is you opt'd for RAID0 because you believe you have a need for all of the IOPS in the world, yet don't care about backups.
But you are missing critical pieces of this design like virtualization, ram cache etc to get better, safer results.
Are IOPS what you want for heavy duty users are making database writes concurrently all day long? I don't know much about drive characteristics/performance other than the basic throughput stuff. Because backup is streamed out in realtime that's taken care of as far as I'm concerned, part of what makes Raid 0 a candidate at least.
Yes IOPS are the consideration you need to be looking at. What has yet to be answered is how active is this database going to actually be?
Will you have 10,000 people/processes constantly making changes?
Ideally more than that, but it'll be a gradual climb. Right now it's in private alpha w/ ~ 100 users and they post stuff all the time. Once I make it public I imagine the content volume will skyrocket.
MySQL is likely your performance bottleneck there.
-
How is your internet going to serve up all this RAID0 SSD awesomeness?? Do you really have the bandwidth to allow the hardware to be the bottleneck?
-
Copying to the other server is not a backup, FYI.
-
@dashrender said in Is this server strategy reckless and/or insane?:
Copying to the other server is not a backup, FYI.
Not a good one, that's for sure. As there is no way to be certain that the copy is functional.
-
@bnrstnr said in Is this server strategy reckless and/or insane?:
How is your internet going to serve up all this RAID0 SSD awesomeness?? Do you really have the bandwidth to allow the hardware to be the bottleneck?
A combination of things, I'm architecting the front-end in a way that it sends the bare minimum out to the user on each request and uses persistent libraries to construct the interfaces to decimate the amount of transfer in general, all of the media and static resources are served out by a CDN, etc. But yeah, I don't think bandwidth will be the issue, but the datacenter I use has super duper bandwidth options if it gets to that point from what I understand.
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
@dashrender said in Is this server strategy reckless and/or insane?:
Copying to the other server is not a backup, FYI.
Not a good one, that's for sure. As there is no way to be certain that the copy is functional.
What do you mean? The live sites will be serving from both copies of the database, which is the evidence/certainty that it's functional, no?
-
@dashrender said in Is this server strategy reckless and/or insane?:
Copying to the other server is not a backup, FYI.
I don't think he means that. He has an HA pair AND he's taking a backup from what I saw.
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
@dashrender said in Is this server strategy reckless and/or insane?:
Copying to the other server is not a backup, FYI.
Not a good one, that's for sure. As there is no way to be certain that the copy is functional.
What do you mean? It's a live cluster. That is definitely being testing constantly. It's mirrored, live copies. THe backup itself, that he has to test offline.
-
How are you confirming the second server is hosting access to this site?
So this is a active/active setup, correct?
-
@dustinb3403 said in Is this server strategy reckless and/or insane?:
How are you confirming the second server is hosting access to this site?
So this is a active/active setup, correct?
Yes, it is live/live.
-
Has anyone mentioned going OBR5 instead of split arrays yet?
Also, I'd spend the little extra money for the Pro edition of the Samsung 850 drives if you want to use commodity parts rather than Dell supplied ones.
-
@travisdh1 said in Is this server strategy reckless and/or insane?:
Has anyone mentioned going OBR5 instead of split arrays yet?
Also, I'd spend the little extra money for the Pro edition of the Samsung 850 drives if you want to use commodity parts rather than Dell supplied ones.
People did suggest OBR5, yep. The benchmarks I ran ( see the large Crystal DiskMark grid below ) made me feel like I'm going to be giving up a lot of performance for not that much additional peace of mind w/ a 5 given my set up and the ability of either server to temporarily take over duties in a pinch. My overarching goal is for most requests to be as close to perceptibly instant as possible most of the time, w/ some downtime being acceptable.
The drives are all Pros, good tip, thanks.
-
@creayt said in Is this server strategy reckless and/or insane?:
@travisdh1 said in Is this server strategy reckless and/or insane?:
Has anyone mentioned going OBR5 instead of split arrays yet?
Also, I'd spend the little extra money for the Pro edition of the Samsung 850 drives if you want to use commodity parts rather than Dell supplied ones.
People did suggest OBR5, yep. The benchmarks I ran ( see the large Crystal DiskMark grid below ) made me feel like I'm going to be giving up a lot of performance for not that much additional peace of mind w/ a 5 given my set up and the ability of either server to temporarily take over duties in a pinch. My overarching goal is for most requests to be as close to perceptibly instant as possible most of the time, w/ some downtime being acceptable.
Sounds to me like you've thought everything through and are aware of all the pitfalls at least, even if I do think you're worrying overmuch about the performance piece. I'm more focused on that for whatever reason, than that you have an effective network level RAID1.
-
@creayt said in Is this server strategy reckless and/or insane?:
@travisdh1 said in Is this server strategy reckless and/or insane?:
Has anyone mentioned going OBR5 instead of split arrays yet?
Also, I'd spend the little extra money for the Pro edition of the Samsung 850 drives if you want to use commodity parts rather than Dell supplied ones.
People did suggest OBR5, yep. The benchmarks I ran ( see the large Crystal DiskMark grid below ) made me feel like I'm going to be giving up a lot of performance for not that much additional peace of mind w/ a 5 given my set up and the ability of either server to temporarily take over duties in a pinch. My overarching goal is for most requests to be as close to perceptibly instant as possible most of the time, w/ some downtime being acceptable.
The drives are all Pros, good tip, thanks.
The big question is... is it performance that affects the application? Benchmarks and raw numbers don't matter all that much. What matters is how the app is impacted. That's why people are asking about the WAN and other components. Getting that kind of performance on such a small web app typically is all throw away performance. Not necessarily, but often.
-
@scottalanmiller said in Is this server strategy reckless and/or insane?:
@creayt said in Is this server strategy reckless and/or insane?:
@travisdh1 said in Is this server strategy reckless and/or insane?:
Has anyone mentioned going OBR5 instead of split arrays yet?
Also, I'd spend the little extra money for the Pro edition of the Samsung 850 drives if you want to use commodity parts rather than Dell supplied ones.
People did suggest OBR5, yep. The benchmarks I ran ( see the large Crystal DiskMark grid below ) made me feel like I'm going to be giving up a lot of performance for not that much additional peace of mind w/ a 5 given my set up and the ability of either server to temporarily take over duties in a pinch. My overarching goal is for most requests to be as close to perceptibly instant as possible most of the time, w/ some downtime being acceptable.
The drives are all Pros, good tip, thanks.
The big question is... is it performance that affects the application? Benchmarks and raw numbers don't matter all that much. What matters is how the app is impacted. That's why people are asking about the WAN and other components. Getting that kind of performance on such a small web app typically is all throw away performance. Not necessarily, but often.
It's heavily realtime-oriented, by which I mean I'm going to be attempting to stream the presence and actions of users to other users in real time and let them see what the other is doing Google Docs style. The ability to retrieve a good handful of information from MySQL per request in as close to 0 ms as possible is very important for the effect to work correctly, hence wanting to keep the app server and database on the same machine for example. Every little ms counts.
