You're missing EVGA: Power supply and extra cables Mouse and mousepad Graphics card waterblock and backplate Many other things http://www.evga.com/Products/BrowseAll.aspx
Lookin' good. Btw, read this: http://hackaday.com/2016/02/28/introducing-the-raspberry-pi-3/ and then tell me your thoughts.
So i have 10.7 tb of storage total. probably overkill, but i never delete anything plus it will last me a while
some of said features are actually very important, one said feature is wheel support, this new apex version has NONE and last i checked that's a pretty important feature for a RACING video game it also has no multi-gpu support (and they advertise 4K60FPS, pretty sure no single gpu is going to manage that very well, at least not without seriously cutting back the rest of the graphics settings) that said, it is a good thing that this is happening as like everyone else has already said: WHOO, FUTURE FORZAS ON PC (looking forward to some 60FPS horizon, or does this only apply to the main motorsport series?)
No wheel support at launch, doesn't mean it won't come soon. The video ran it at 4K60fps on a 980ti, DX12 means a big gain for Nvidia and even more so with AMD GPU's. Would be really surprised if there wasn't a good range of cards that could run it that well. The cut down features I mentioned are content more than anything. Most if not all of the core gameplay features will be there from what I've heard. The only real negative aspect so far is the god awful windows store exclusivity.
still pretty stupid to not support sli/crossfire/slifire(as dx12 supports using multiple brand gpu's at the same time) in this day and age though, pretty sure even beam supports it if you force it in the graphics control panel 100% agreed on windows store though, fuck that piece of crap (seriously microsoft, no one wants to use the windows store, just bring it to steam with a requirement of windows 10 (i'm sure steam has someway to make it only installable on windows 10, as AFAIK this apex game is also going to be dx12 only, which is why it's w10 only)) while i don't have multiple HDD's myself (multiple partitions instead) i personally differentiate by giving my partitions appropriate names based on whats in them
I just cram all my junk into a folder and call it good. --- Post updated --- Hey kid. Wanna see how a Hard Disk Drive works?
Code: import datetime, sys, math # Function to print message def print_prime(x): print " Prime : %7i " %x # Function to search for prime numbers # within number range def find_primes(upper_limit): count = 0 candidate = 3 while(candidate <= upper_limit): trial_divisor = 2 prime = 1 # assume it's prime while(trial_divisor**2 <= candidate and prime): if(candidate%trial_divisor == 0): prime = 0 # it isn't prime trial_divisor+=1 if(prime): print_prime(candidate) count += 1 candidate += 2 return count # Check if the script was called with a # parameter. Use that as the upper limit # of numbers to search if len(sys.argv) != 2: upper_limit=1000000 else: upper_limit=int(sys.argv[1]) # Record the current time startTime = datetime.datetime.now() # Start the process print "" print "Starting ..." print "" count = find_primes(upper_limit) print "" # Measure and print the elapsed time elapsed=datetime.datetime.now()-startTime print " Found %d primes in %s" %(count,elapsed) print "" Ran this in ironPython on both an intel i3-3217u (mobile i3, dual core+HT, 1.8ghz) powered laptop running windows 8 64 bit (tested in both 32 and 64 bit) and an intel atom Z3735G (1.33ghz quad core, turbo to 1.86) powered tablet running windows 10 32 bit. Results are the time taken to calculate every prime number up to 1 million, hours, minutes, seconds. i3-3217U in 32 bit: 0:00:27.392 i3-3217U in 64 bit: 0:00:22.902 Z3735G in 32 bit: 0:02:14.079 Significantly. The new raspberry pi 3 supposedly does this in 0:01:07 however that is running a standard python 2 interpreter on debian on ARMv8 in 64 bit. Currently have no intention of installing plain python 2 on this machine so we wont get any direct comparisons, and tablet was in battery saver mode so I doubt what going into its full 1.86ghz turbo. --- Post updated --- Woah, 32 bit pypy on the 3217U, 14 seconds. --- Post updated --- pypy and ipy results with modified script with line 20 commented out. ipy: 15 seconds pypy: sub 1 second. --- Post updated --- Here we go, more thread spam. Stackless python with print statements: 34 seconds Stackless python without print statements: 15 seconds. Python 2 with print statements: 45 seconds Python 2 without print statements: 23 seconds
PyPy on my computer (sig) has been averaging about 0.38 seconds (having been slightly streamlined) without print statements. Tomorrow I'm going to add a logging feature that includes system info if Python can pull it and the times. If Python would push a single thread to max usage, then I imagine this would be a very good singlethreaded benchmark and possibly stress test.
I have, no consistency. However, that's a shared user server. I'm not the only one with access to cpu time and likely wasn't the only one online. it's all 30-40 range but without any slowdowns due to printing as far as I can tell