Help Does Cpu Strength Mean Much When Dealing With L2Off?

[JulietCapulet]

Basically I'm curious if its too much of a deal for L2Off to be hosted for example between E3-1271V3 and Dual E5-2620.

[xeL]

I use vang files c6 on e3 1220 v2 dual core and cpu stays at 5% only

[JulietCapulet]

Got it, thanks a lot bud.

[Asmodeus]

You can host it in nahaleem or anything. In any case c4 was built on 2005~ and guess what cpu's they used back then. However, what matters most is IOPS and ram.

[JulietCapulet]

You can host it in nahaleem or anything. In any case c4 was built on 2005~ and guess what cpu's they used back then. However, what matters most is IOPS and ram.

Fair enough; does 1TB SSD with no raid sound adequate? or should i go with 2x 512GB SSD and raid?

[xeL]

Fair enough; does 1TB SSD with no raid sound adequate? or should i go with 2x 512GB SSD and raid?

Ofc raid for safety.

[xxdem]

Ofc raid for safety.

 

Do you actually know that there are raid configurations that do exactly the opposite than increasing safety? Raid zero for instance. The correct answer would be go 2x512 @ Raid 1

[xeL]

Do you actually know that there are raid configurations that do exactly the opposite than increasing safety? Raid zero for instance. The correct answer would be go 2x512 @ Raid 1

I didn't mention because is clearly that only raid 1 is good for backup option. Raid 0 is excluded in this case. Specially when opening a live server. Well if you want raid 0 is ok but i realy don't recommand. Edited October 8, 2015 by xeL

[Asmodeus]

Actually raid 0 splits the calculations performed on each drive. Which, incase we have 2 drives, halves the operations of each one and therefore the lifetime expectancy may also be double. Regarding live servers, what you seek is speed. You shouldn't look for "safety" on drives, since the biggest downtime expected is the changing of the failed drive.

 

The solution to security is called "cloud remote backup" of the database, plus monitoring in case of ssds since they degrade before failing.

 

RAID1 helps avoiding downtimes in case of drive failure, but don't rely your server on local-only "security".

[xeL]

Actually raid 0 splits the calculations performed on each drive. Which, incase we have 2 drives, halves the operations of each one and therefore the lifetime expectancy may also be double. Regarding live servers, what you seek is speed. You shouldn't look for "safety" on drives, since the biggest downtime expected is the changing of the failed drive.

 

The solution to security is called "cloud remote backup" of the database, plus monitoring in case of ssds since they degrade before failing.

 

RAID1 helps avoiding downtimes in case of drive failure, but don't rely your server on local-only "security".

I still recommand sas . l2 off works ok on all. The diferance will be on loading and not on game play. That why recommand it raid 1 anyway is up to him . He can use even 1 ssd with cloud db backup.

[Asmodeus]

SAS are speed oriented HDDs.

 

Storage drives are all about their lifespan,speed and capacity.

 

SAS are speed oriented HDDs with the same lifespan as normal HDDs, their capacity is low tho, sometimes lower than SSDs and their speed is way lower than SSDs, not to mention the ridiculus price of them at 2k15.

 

If the setup is to be a RAID1 array, then SAS are worthless in case of server leasing. While you lease a server you don't care for how many failed drives you have as they are replaced for free as long as you use the leased server. So, as long as you don't have both drives failed which can be achieved easily by monitoring the errors,health on S.M.A.R.T., you won't have any downtime at all, because when you replace a drive the other one copies itself to the new while the server runs!

 

SAS may only be usefull due to their longer lifespan when you OWN the server hardware to avoid getting new drives.

 

My 2 cents.

 

 

(lease means rent or whatever is widely called)

[scrubs]

SAN + Raid 5 if you got money to spend.

Otherwise, Raid 1 is quite alright with 2x SAS or just 2x normal HDD.

 

Also to be on the safe side, cloud storage backups for database.

If you use ESXi I'd recommend setting up daily snapshots of the VM which stores it on another datastore than the vmdk.

[Asmodeus]

SAN + Raid 5 if you got money to spend.

Otherwise, Raid 1 is quite alright with 2x SAS or just 2x normal HDD.

 

Also to be on the safe side, cloud storage backups for database.

If you use ESXi I'd recommend setting up daily snapshots of the VM which stores it on another datastore than the vmdk.

Regarding SAN, no comment at all.

 

Any virtualization is a DON'T!

Virtual enviroment has limitations in kernel and it may cause issues!

Learned it the hard way.

[scrubs]

Regarding SAN, no comment at all.

 

Any virtualization is a DON'T!

Virtual enviroment has limitations in kernel and it may cause issues!

Learned it the hard way.

 

I work in IT infrastructure, if you use proper virtual environments then it shouldn't be a problem.

Now this is not related to L2 at all.

 

Currently got over 500 virtual servers, anything from high traffic APP servers to high CPU/RAM consuming databases... list goes on and on, no issues at all.

Actually virtual hardware works more efficient than if you ran everything off the physical server.

 

It all depends on the setup and configuration.

[Asmodeus]

I'm not here to doubt your work or anything, neither to discuss it much.

We're talking l2 setup here and people tend to look for plug&play solutions with minimal configuration, so, my suggestion is to always use remote backup and fastest speeds because you don't pay for replacement drives.. If raid1 is possible then use it, it will help avoiding downtimes.

 

That's all.

[scrubs]

I'm not here to doubt your work or anything, neither to discuss it much.

We're talking l2 setup here and people tend to look for plug&play solutions with minimal configuration, so, my suggestion is to always use remote backup and fastest speeds because you don't pay for replacement drives.. If raid1 is possible then use it, it will help avoiding downtimes.

 

That's all.

 

Hehe it kinda went out of topic there didn't it :) 

 

I agree with using Raid 1 in this case though. 

And as I mentioned before, backing up daily db dump to cloud isn't a bad idea either.