We constantly update our data to provide you with latest and most accurate requirements. Below are Rust requirements details for CPU, operating system, graphics and sound cards, required disk space and more for each of the supported platforms.
Storage Additional Notes SSD is highly recommended or expect longer than average load times. As for a graphics card, it should be GTX 670 2 GB / AMD R9 280 better, and it should support Direct X Version 11.
When a solid state disk is presented with a 4K random I/O workload, if it can't figure out some way to aggregate and parallelize the requests, it will end up bottle necking at much lower speeds, dictated by how quickly a single cell of flash media can read or write a block of data. You should generally expect throughput to be discussed in terms of how much data a disk moves under optimal conditions, and Ions in terms of the “high-end grunt” the disk is capable of even under the worst workload.
Advertisement Read cache keeps the system from having to tie up storage with unnecessary repeated requests for the same blocks over and over again. If your operating system has plenty of RAM available, each time it reads data from disk, it keeps a copy of it lying around in memory.
Fit is short for Flexible Input/Output tester and can be configured to model nearly any storage workload under the sun. We're not going to be quite that specific here, but we will use fit to model and report on some key usage patterns common to desktop and server storage.
If your OS needs to write a couple of lines to a system log, or read a few KB of data from a system library, your “sequential” read or write immediately becomes, effectively, 1 MB random I/O as it shares time with the other process. If you're sufficiently paranoid, you may wish to download the file, inspect it, and then run it as separate steps instead.
Where this happens most frequently in real life: copying home directories and dot files, manipulating email stuff, some database operations, source code trees. The server just beneath it in the rack only managed 33 MiB/sec on its “high-performance” 7200RPM rust disks... but even then, the vast majority of that speed is because the data is being written asynchronously, allowing the operating system to batch it up into larger, more efficient write operations.
If we add the argument sync=1, forcing the operating system to perform synchronous writes (calling sync after each block of data is written) the picture gets much more grim: 2.6 MiB/sec on the high-performance SSDs but only 184 KiB/sec on the “high-performance” rust. This time, we're creating 16 separate 256 MB files (still totaling 4 GB, when all put together) and we're issuing 64 KB block sized random write operations.
This is also a pretty good, slightly pessimistic approximation of a busy, multi-user system like a NAS, which needs to handle multiple 1 MB operations simultaneously for different users. If several people or processes are trying to read or write big files (photos, movies, whatever) at once, the OS tries to feed them all data simultaneously.
Besides, if literally any other disk activity is requested simultaneously with a contiguous write, the “contiguous” write devolves to this level of performance pretty much instantly, so this is a much more realistic test of the upper end of storage performance on a typical system. Rust disks will tend to provide a much more consistent, though typically lower, throughput across the run.
Once those get exhausted, the disk has to drop to writing directly to the much slower TLC/QC media where the data eventually lands. If you have any doubt at all about a TLC or QC disk's ability to sustain heavy writes, you may want to experimentally extend your time duration here.
These caps can be frustrating in an age of high-quality streaming videos and services that depend on plentiful bandwidth. A few simple tips can help you make the most of that limited bandwidth if you can’t find a better ISP.
Keeping an eye on your bandwidth usage is key if you have a fairly low cap and are worried about going over it. Bear in mind that it may not update instantly, so you may have to wait a day or so to see the latest information.
For example, Windows 8 has a bandwidth-usage tracking feature that can give you an idea of how much data you’ve transmitted in the last month. If you want to stream videos while not losing your entire bandwidth allotment, you can generally turn down the quality settings.
For example, with Netflix you can visit the Account screen and click Playback settings to select a data usage level. Visit the Playback section in YouTube’s settings and select the “I have a slow connection.
YouTube will default to slower videos even if you have a faster connection, saving bandwidth. When you start watching a video, you’ll usually find quality options in the player too.
Advertisements are one thing, but wasting precious bandwidth on large, heavy ads is another. Tricks like this one are more useful when you’re tethering to a smartphone connection with extremely limited bandwidth, but they can help in a pinch.
Bear in mind that, while images can be large, they’re not anywhere near as heavy as a streaming video or animated Flash advertisement. Even ISPs that don’t limit bandwidth usage may slow down (or throttle) your connection during the day and speed it up at night.