• Content count

  • Joined

  • Last visited

  • Days Won


cinoaz last won the day on September 21 2015

cinoaz had the most liked content!

About cinoaz

  • Rank
    Advanced Member
  • Birthday

Recent Profile Visitors

528 profile views
  1. Oh, Tim sold it, to ahem "investors". Good luck Tim, see you on the virtual gaming battlefield soon.
  2. Yep, I see similar behavior on the 3.0 Beta Here's a video of the issue:
  3. Yeah, really old thread, just providing feedback.... DIMMDRIVE moves the game files you choose to RAM, maybe it's all the game files, but, it's really not. You see, when the game runs it's making calls to many supporting programs that have nothing to do with the game. Many of these are the O/S directly(i.e. Directx, file packing/depacking, audio stream, etc). So although you "think" the entire game is running from DIMMDRIVE, it's really not. If you installed your O/S on a pretty quick SSD or such, that will be better. If your O/S is hampered by a mediocre drive, well, unfortunately that's that. I learned this a few years back while doing some of my own in depth stuff similar to RAMDRIVE (using batch files instead). I saw tons of queries to my C Drive when running games, so although I had a decent SSD, it's still nowhere close to RAM speed (lol, Last Starfighter quote and I didn't even intend it)
  4. Tim, Glad to see things are still banging away. I just downloaded the 3.0 Beta but I didn't see the option we talked about a few years back: I see in USB 3.0 Turbo my Platter drives show up, but my C: drive using the Samsung EVO mSata doesn't. Back to my original post, If I created a temp folder on my C drive, large enough to hold, say a single game (8GB for example), then I move the game from my Platter drive to the mSata folder and create the symlinks for the O/S. Now I'm running off of mSata. Now, I can tell Dimmdrive to grab the most used files for the game and load into RAMDRIVE. When RAMDRIVE does, it's going to go to the platter drive, the O/S will redirect it to my mSata, DIMMDRIVE will grab the files from mSata, create the symlinks, and load it into memory. IN the end, the game is running in Hybrid, some off my mSata and some off of RAMDRIVE but NONE off very slow platter...
  5. Actually, remove the platter from the equation totally. Right now, Steam points to my platter drive for all my games (D: drive) I move the game from my platter drive to the SSD drive(X: Drive) and create the symlinks via Batch file. I then turn on DD. DD goes to my platter drive (D:) and is redirected to my SSD drive (X: drive) via the symlinks. I configure DD to grab the most used files (using ProcMon) and push them to the RAMDRIVE. When DD launches, it moves files to the RAMDRIVE but it's actually creating the symlinks on the SSD Drive. It's a double redirection via the O/S. So, ALL of the game files run off of the combined SSD and RAMDRIVE, the platter sits idle. When I reboot my machine, my top played games are already on the SSD drive. Thus, when I turn on my RAMDRIVE, on average, there's less files that need to be copied and the game is ready sooner. Now, do I need to move files to RAMDRIVE in this scenario. No. I could be very happy with just the performance gain I get for moving files from the platter to the SSD raid. Being able to redirect once again to the RAMDRIVE is just that much cooler and better. I envision games having two sliders in DD. One moves the game from the platter to the SSD. Then there's a second button called "BOOST", that create the RAMDRIVE and moves files onto it, as configured. Not everyone has oodles of system memory, but, pretty much everyone can afford a couple of SSDs and see their performance increase almost 10 fold, which, then will want them to increase it even more, then there you go. Regarding the "Auto-File feature". I believe this has been said before, but, allow a user community to submit configurations for games. I mean, I did all this work to identify the files for CoH2 and I'm enjoying the results. The XML structure is pretty straight forward, actually, kudos for your work I would've gone with xml or yaml myself. Should be a simple "search and replace" in the xml file for the >linked< tag. No need to share the whole file because who knows directory names and structures, but then again, that's why you designed it the way you did :-)
  6. Hey Tim, Could you elaborate on "Make sure you blast away your old DD config..." I uninstalled DD via steam, reinstalled via steam and when I try to create the RAM drive on Windows 10....well, things go wonky. It takes fore........e...v...e....r.... for the drive to be created. Once it does, windows say "You have to format first" and I need to give the new drive a name. I do that, however, once in a while the RAM drive just disappears. Strangest thing ever. I then turn off Ramdrive from DD. Then it takes fore........e.....v.......e........r for it to complete. Any words of wisdom?
  7. DIMMDRIVE gives you an option to select certain files, not necessarilly the whole directory. Using PROCMON, you can see which files of the games are used the most. Set aside System Memory for those few files, configure DD just for those few files. The benefit, is actually huge. For example, Company of Heroes 2. I did a trace and notice that just a handful of packed files kept getting hit. Total was about 8gigs of files, compared the game that takes up 21Gig on the disk. So, I could just load the subset of files and see a HUGE gain. Another option(which I use)
  8. Sorry, it was meant to be in jest, sorta. I was really hoping you would implement the option to cache to a spare drive instead of just SysMemory. You indicated this was to be made available in the next rev but wasn't part of the 1.25 release. Sooo, to keep things lighthearted, it was more of hyperbole final statement. No, I don't expect to work with you on this. This is your thing, I'm just a customer. It was more of "please....please....add it in natively.." Thanks For example, CrystalMark I get ~ 150MB/s reads from my spindle drive ~490MB/s reads from my SSD drives ~4500MB/s reads from my System Memory So, yes, System Memory is the "Best", but, I'm currently running two 120GB SSD drives, Raid 0. I get 240GB for temporary storage of my games with ~1000MB/s read performance, of course, using my symlink method defined above. The best scenario is to idenify the top hitters to SystemMemory, the rest to SSD and your SPINDLE DRIVE for the mass quantities of storage. Thus, you limit your System Memory cache but still get really good performance on everything else. To give an example. From left to right: 7200RPM Spindle Drive 240GB SSD 6gb/s 2 120GB SSD 6gb/s in RAID 0 DIMMDRIVE RamDrive Granted, nothing comes close to the Ramdrive, but, two 120GB SSDs cost me ~$100 bucks, so I'm getting basically maxed Serial ATA 3.0 (6gb/s) throughputs (Realistic, not theoretical calculations). The cost of System Memory is a major expense in order to have enough spare to push today's games to. No denying it's performance, just cost of getting there, however, look, for $100 your trashing spindle drives, you're twice as fast as a single SSD and when DimmDrive supports caching to SSDs natively, for the price and performance, yeah, you are sitting pretty. Now for the next challenge, do a double symlink. Push the entire game to the SSD RAID array, create the symlink, then push the MOST USED files from a game to the RAMDRIVE and create a symlink from the symlink....hhhmmmm
  9. DIMMDRIVE uses the spare RAM in your system to build a pseudo drive which it then loads and runs game from. Open DIMMDRIVE, set the amount of System Ram to set aside. Remember your O/S and Game both need system ram, so, don't go overboard with for DIMMDRIVE. Go to DIMMDRIVE library, find your game, and turn slider on. DIMMDRIVE will then copy your game files to the RAMDRIVE, when it's ready, launch the game.
  10. Yo, if anyone is still using this method in Windows 10. Even tho u turn off UAC, you still need to run BATCH files and such as an Administrator otherwise the SymLinks won't get created. To eliminate the need to right click on batch file and say run as admin, there is a workaround. Create the batch file. Now create a shortcut to that batch file. Right click on shortcut, click ADVANCED, put a check mark in RUN AS ADMIN. Now, just double click the shortcut and it's ran as admin and bingo, all good. You skip having to right click the file and say run as admin. As an option, you can skip launching the executable via the batch file altogether. Just delete everything under the "pause" command in my example. Once the files are copied and symlinks are created, you can launch the game via your Steam Library just as always. What is pretty cool, you can leave all your games on the SSD drive as long as you want. The only hitch, if you need to make room on the SSD for another game, you need to resync the files from the SSD DIMMDRIVE back to the source folder so any changes (game saves, profile updates, etc) are copied from the temp SSD file back to the original source. Another cool option. Nothing is lost if your computer locks up or restarts. Since all the files are on the SSD, not the RAM, nothing is lost during reboots and such. So, if you reboot, no need to resync or redo your symlinks, they are all still there. So, once you create the symlinks for your game, you're pretty much done. Leave them on the SSD as long as you want. You don't need to wait for a RAMDRIVE to be created, you don't need to copy files over and over. Do it once, now just launch via Steam. Hopefully that's clear, if not, send me a pm, no biggie.
  11. Well, Took a bit of a hiatus from DIMMDRIVE, I was all excited to come back and see that I can cache to my blank SSD drive, loaded up DimmDrive and...................ugh.... Still not implemented !?!?!?!?!?! Tim, whats going on man, this really isn't that big of a deal. I'm going back to Batch files...oh the humanity !!!!! Tim, show the love, show the care, show how much paying customers like me are worthwhile of having ... Let's get this in, a quick release, you and me, what do ya say?
  12. I use PROCMON now to see what files are getting hit the most. Thxs to another forum user in helping me understand that tool. I use afterburner for my games so I know how far I can push things in terms of setting before my system starts to "buckle" a bit. The solution could be as complex as PROCMON report, or, a much simpler "Gauge" that just displays the Read/Writes currently going through the RAMDISK. The main point is determining if DIMMDRIVE is really applicable to the game itself. Playing DOTA2, most files are loaded upon startup. There's not much going on during gameplay, so DIMMDRIVE really doesn't affect DOTA2. Due to other "code" stuff, even loading the game doesn't change much. However, if I had a some monitor, say in Afterburner where I constantly see my Drive Access pegged out, now there's a game DIMMDRIVE could really use. The root issue was whether or not the game files were actually being loaded from DIMMDRIVE or was it a bunch of smoke and mirrors. Having done further analysis I answered that question, but for new users the question remains. How much performance increase am I getting for the games I play. Don't give me general numbers, let me see for myself.
  13. So, Wondering, could you load an O/S into a RAMDRIVE? Not sure the outcome, just having fun with the "how would you do it" aspect... I'm thinking...create an WIN image, boot using simple loader, create c:\ ramdrive, extract image into ramdrive, reboot but not power off, BIOS picks up C Drive, boots..... Hhmmm....
  14. I think if you search for my posts you will see that I've done my fair share of poking sticks at DD. What isn't mentioned is Windows Caching too, which, takes you most accessed files and sticks it in RAM. Lots of factors here. The point being, although some people say it boosts your FPS, honestly I doubt it does in any major discernable way. What it does do is creates a pretty slick interface to create RAMDRIVEs easily and it intergrates into Steam. A newer version will allow you to create drives on SSDs, which, I see as a much more viable economical position. 120GB SSDs are relatively cheap. By using the features of shifting games from one drive to the next, you get all the benefits of your 4TB spindle to load all your games to and then offload the one game your playing to an SSD temporarily without having to deal with anything, just a slider on DD GUI. DD moves everything around in the background. I did the same thing DD is doing via batch files. It's no secret, no black magic. What DD does it does so with a very simple, clean, easy to use interface. I've also used DD to create blank RAMDRIVEs for multitude of other purposes. Anything that requires high number of Disk Access I do off of RAMDRIVE. The ONLY discernable difference are games that dynamically load large compressed files for textures and stuff. Any game that does this, DD will be a huge benefit. I'm currently not playing any game that really utilizes this, but I still use DD, not because of "Oh My God hold onto your seat" performance gains in typical games, but, the increase is noticable and the more you use it, the more you want to use it. In the end, what DD is to me, is starting to shine a light on other bottlenecks in a system that were masked due to the limits of the SATA interface. I'm looking for ways to speed those things up. It's not a big bang, but, it gives a foothold to move the entire School Bus forward. I don't agree with using RAPID on these tests, it doesn't reflect the true bottleneck of the SSD which is the SATA interface itself. Everyone knows how to game benchmarks, even DD is a bit guilty on this front. But if you look at the interface specs alone, it's clear the advantages are there. The secret, to figure out how to fully utilize it, that's a job I look forward to.
  15. He should have done tests with RAPID off, otherwise it's just RAMDRIVE vs RAMDRIVE and useless.