Jump to content
SAU Community

Recommended Posts

That applies to the Intel X25 only. There are many other types of SSD, intel do not have the monopoly on them, nor are they to be considered competent in SSD technology. No other SSD has issues with 'sector remap fragmentation'. I have a runcore SSD in my EEE and they do not suffer from any said problem.

Intel != all ssd's. TBH it sounds like you're just repeating what you've read from slashdot or arstechnica.

Intel > all SSD's

Load times are no doubt impressive with SSD's however their write performance sucks. Intel owns in this department offering performance similar to a mechanical HD where as the other SSD's fall far behind which is where the old 'stuttering' problem individuals complain about.

IMO Intel is SSD at the moment no other drive comes near it.

My little old AAKS peaks at 120mb/s holds that until close to 200gb then starts to tail off achieving an average read over 640gb of ~92mb/s according to the ol' hd tach.

The 'other' SSD's that don't have the issue Intel have simply suck when it comes to write speeds. Write speeds are important for a workhorse, again... SSD = great for a little lappy that doesn't see any 'real' usage.

I would consider an SSD for installing a few games on but even then for the $$ its hardly worth it.

Unless the other SSD's can sort out their write speeds and stutter as well as Intel sorting out their low level fragmentation issues I won't be jumping to SSD.

The SSD in the Asus EEPC is great but honestly its not really noticably faster than the AAKS HD apart from booting Windows.

Probably a bad example of a performance SSD in those Asus EEPC's but they are great for what they are, yes I've noticed a little stuttering with that SSD which sucks but you learn to live with it.

If you don't notice any stuttering etc what SSD is it you use?

Intel > all SSD's

Load times are no doubt impressive with SSD's however their write performance sucks. Intel owns in this department offering performance similar to a mechanical HD where as the other SSD's fall far behind which is where the old 'stuttering' problem individuals complain about.

IMO Intel is SSD at the moment no other drive comes near it.

If you don't notice any stuttering etc what SSD is it you use?

I use a runcore SATA mini PCI-E aftermarket replacement. Its a 32gb model. I've ran the benchmarks using HDParm on both my laptop and the SSD in the EEE.

the one in the EEE gets 125MB per second read, and 55MB per second write. My WD Raptor does 55mb Writes and 60mb Reads. The Green WD drive I have as my primary data store gets 55MB per sec reads and 45MB per second write. The SSD write speeds equal the WD Raptor I have in my main PC.

Intel do not own the SSD market. Not even close. Their idea of a wear levelling algorithm is to simply split the file up into multiple fragments and randomly allocate a logical block. Not a good idea.

There are two different types of SSD technology. MLC (Multi level cell - slower, less reliable) and SLC (Single level cell). SLC is much faster than MLC but at a greater cost, hence it doesn't get used quite as much. That said, MLC drives are getting faster at writes - indeed, the SSD in the EEE (Runcore) is an MLC based drive. The RunCore SSD is about 2.5 times as fast as an early MLC on reads and 6-8 times as fast on writes.

To compare with the MLC that came with the EEE - 8gigs. It has writes of 2MB a second max and 12MB/s reads. Once replaced with a fast runcore module, the 'stuttering' problem (which was Windows writing/changing files) simply vanishes. It makes the EEE like a new PC.

FYI - http://www.voitech.com.au/products/runcore...1-and-s101.html

-D

then something is wrong there damo

i have been using a pretty new HP and would say that the HP shits all over the dell with the same specs

how can 2 pcs have the same specs and have such a big performance difference...

god i hate dell pc's

then something is wrong there damo

i have been using a pretty new HP and would say that the HP shits all over the dell with the same specs

how can 2 pcs have the same specs and have such a big performance difference...

god i hate dell pc's

Just answered your own question :) we use Dell pc's. Optiplex 745, dunno the specs, but id rather use a piece of paper.

do a "start", then "run" and then type in "dxdiag"

that will give you the specs of your PC

We use Dell Optiplex 755 or HP 7800 DC

Both of them are Dual Core, 2 GB RAM, DVI card etc etc

love the HP

Intel Core 2 6300 @ 1.86GHz, 512mb RAM. In brackets it says (2 CPU's) :D

Core 2's Duos have two cores per die (and quads have 4) ;P Unlike a P4 with hyperthreading which reports back two cores but actually only has one...

-D

Intel Core 2 6300 @ 1.86GHz, 512mb RAM. In brackets it says (2 CPU's) :D

there is your answer damo...core 2 = 2 cores

shit you need more RAM and a better CPU lol

Mine at work is a Core 2 Duo, 2.8GHz, 2018 RAM, 384 MB Video Card etc

works like a dream

Ok here's one for ya guys, got a 300GB hard drive that I store some of my files on. The other day it took a shit, so now when I boot up the PC with the 300GB in, it hangs while loading Windows. I've tried it in 3 different PC's now and same problem. Tried it again today and BAM, in it went, had access to all files, etc. Then I stupidly restarted and it all went wrong again. Any ideas how I can recover the files off this hard drive? I should have grabbed them when I did but as I said, stupidly reset :cool:

Usually I have no problems recovering atleast some data from dicky hard drives but this one has me stumped

its munted, if it boots again be ready to get all the files off it quick smart.

data recovery programs usually only work if the drive works, try booting using Heirin (sp?) it has tools to fix up all major brand hard drives, might get her up n running again

i have a few paper weights like ur drive

yeah thats the one

i have a few that spool up just fine when powered up, but are cactus..

one of them however i saved using the boot disk, is a WD drive, and i had it running for a good 6 months afterwards in my firewall

there is your answer damo...core 2 = 2 cores

shit you need more RAM and a better CPU lol

Mine at work is a Core 2 Duo, 2.8GHz, 2018 RAM, 384 MB Video Card etc

works like a dream

I've been using an EEEPC the past month or so while my desktop is being built. It drives me nuts with it's slowness - loading any webpage it lags up for a few seconds - its worse when I'm loading pages on multiple tabs. Cant wait til my new computer built - so far its half built and saving up to grab the rest then I can finish it off and use it.

there is your answer damo...core 2 = 2 cores

Thats not 100% correct, the core 2 doesn't means 2 cores, as the Quad CPUs is also called Core 2 (my Q6600 has the Intel Core 2 Quad sticker) the "2" refers to the 2nd major refresh of the Intel core architecture, there was an original Intel Core Duo CPU (no 2 in the name) it was dual core & it was released in the laptop market only, it had the prefix "T" for the CPU models (my mum's laptop had one of those CPUs; a T2500 which ran @ 2Ghz).

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • I had 3 counts over the last couple of weeks once where i got stranded at a jdm paint yard booking in some work. 2nd time was moving the car into the drive way for the inspection and the 3rd was during the inspection for the co2 leak test. Fix: 1st, car off for a hour and half disconnected battery 10mins 4th try car started 2nd, 5th try started 3rd, countless time starting disconnected battery dude was under the hood listening to the starting sequence fuel pump ect.   
    • This. As for your options - I suggest remote mounting the Nissan sensor further away on a length of steel tube. That tube to have a loop in it to handle vibration, etc etc. You will need to either put a tee and a bleed fitting near the sensor, or crack the fitting at the sensor to bleed it full of oil when you first set it up, otherwise you won't get the line filled. But this is a small problem. Just needs enough access to get it done.
    • The time is always correct. Only the date is wrong. It currently thinks it is January 19. Tomorrow it will say it is January 20. The date and time are ( should be ! ) retrieved from the GPS navigation system.
    • Buy yourself a set of easy outs. See if they will get a good bite in and unthread it.   Very very lucky the whole sender didn't let go while on the track and cost you a motor!
    • Well GTSBoy, prepare yourself further. I did a track day with 1/2 a day prep on Friday, inpromptu. The good news is that I got home, and didn't drive the car into a wall. Everything seemed mostly okay. The car was even a little faster than it was last time. I also got to get some good datalog data too. I also noticed a tiny bit of knock which was (luckily?) recorded. All I know is the knock sensors got recalibrated.... and are notorious for false knock. So I don't know if they are too sensitive, not sensitive enough... or some other third option. But I reduced timing anyway. It wasn't every pull through the session either. Think along the lines of -1 degree of timing for say, three instances while at the top of 4th in a 20 minute all-hot-lap session. Unfortunately at the end of session 2... I noticed a little oil. I borrowed some jack stands and a jack and took a look under there, but as is often the case, messing around with it kinda half cleaned it up, it was not conclusive where it was coming from. I decided to give it another go and see how it was. The amount of oil was maybe one/two small drops. I did another 20 minute session and car went well, and I was just starting to get into it and not be terrified of driving on track. I pulled over and checked in the pits and saw this: This is where I called it, packed up and went home as I live ~20 min from the track with a VERY VERY CLOSE EYE on Oil Pressure on the way home. The volume wasn't much but you never know. I checked it today when I had my own space/tools/time to find out what was going on, wanted to clean it up, run the car and see if any of the fittings from around the oil filter were causing it. I have like.. 5 fittings there, so I suspected one was (hopefully?) the culprit. It became immediately apparent as soon as I looked around more closely. 795d266d-a034-4b8c-89c9-d83860f5d00a.mp4       This is the R34 GTT oil sender connected via an adapter to an oil cooler block I have installed which runs AN lines to my cooler (and back). There's also an oil temp sensor on top.  Just after that video, I attempted to unthread the sensor to see if it's loose/worn and it disintegrated in my hand. So yes. I am glad I noticed that oil because it would appear that complete and utter catastrophic engine failure was about 1 second of engine runtime away. I did try to drill the fitting out, and only succeeded in drilling the middle hole much larger and now there's a... smooth hole in there with what looks like a damn sleeve still incredibly tight in there. Not really sure how to proceed from here. My options: 1) Find someone who can remove the stuck fitting, and use a steel adapter so it won't fatigue? (Female BSPT for the R34 sender to 1/8NPT male - HARD to find). IF it isn't possible to remove - Buy a new block ($320) and have someone tap a new 1/8NPT in the top of it ($????) and hope the steel adapter works better. 2) Buy a new block and give up on the OEM pressure sender for the dash entirely, and use the supplied 1/8 NPT for the oil temp sender. Having the oil pressure read 0 in the dash with the warning lamp will give me a lot of anxiety driving around. I do have the actual GM sensor/sender working, but it needs OBD2 as a gauge. If I'm datalogging I don't actually have a readout of what the gauge is currently displaying. 3) Other? Find a new location for the OEM sender? Though I don't know of anywhere that will work. I also don't know if a steel adapter is actually functionally smart here. It's clearly leveraged itself through vibration of the motor and snapped in half. This doesn't seem like a setup a smart person would replicate given the weight of the OEM sender. Still pretty happy being lucky for once and seeing this at the absolute last moment before bye bye motor in a big way, even if an adapter is apparently 6 weeks+ delivery and I have no way to free the current stuck/potentially destroyed threads in the current oil block.
×
×
  • Create New...