Jump to content

jbartlett

Community Developer
  • Content Count

    1567
  • Joined

  • Last visited

  • Days Won

    7

jbartlett last won the day on August 6 2019

jbartlett had the most liked content!

Community Reputation

184 Very Good

2 Followers

About jbartlett

  • Rank
    John Bartlett
  • Birthday 07/20/1970

Converted

  • Gender
    Male
  • URL
    https://www.youtube.com/c/TheCritterRoom/
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That would be better represented by a color change. The heat map will be a something like an 800x200 grid where the drive size and read speeds are scaled to fit in that. The more times a spot gets hit, the brighter that spot would become. The line between the 11 spots (scanned every 10% plus the start) would be interpolated. Here is a demo that shows a heat map tracking temperatures throughout the year.
  2. I am having issues with the docker honoring the CACHE_SLICE_SIZE setting. I added a setting to the Docker app for this CACHE_SLICE_SIZE variable, setting it to 8m. As expected, the docker refused to start since it detected a change to the CONFIGHASH file. I removed it from the lancache directory and the Docker started up, recreating the CONFIGHASH with: GENERICCACHE_VERSION=2;CACHE_MODE=monolithic;CACHE_SLICE_SIZE=8m;CACHE_KEY=$cacheidentifier$uri$slice_range; However, all of my cache slices are still being limited to 1m. Any ideas?
  3. I have two data points, drive location and speed. I'd need a 3rd data point for a 3D representation, what would that be?
  4. That's basically describing a heatmap. Interesting concept that I'll likely explore - notably because I added a graph with all of the benchmarks using the same revision & RPM and it was just a hot mess of lines.
  5. I just noticed that the two graphs with the multiple groupings both have the same revision number which tells me that Western Digital used the same circuitry with different number of platters. A quick query shows this same trend over multiple vendors. There might be some insight into seeing how the same revision fairs on different drive media configurations.
  6. Docker Version 2.8 has been pushed Don't include floppy devices Multiply the SMART LBA Read/Written values by the Logical Sector Size instead of the Sector Size Add more validation logic to clean up Vendor/Model combinations I have rewritten from the ground up the Hard Drive Database website at http://strangejourney.net/hddb/ to display meaningful benchmark graphs. When viewing benchmark data for a particular drive, a graph line is drawn for each unique drive's most recent benchmark is displayed. If 100 people own a given drive and they've all done one or more benchmarks against that drive and uploaded them, the HDDB would have 100 graph lines for those drives. It gives you an idea as to how stable that model is on performance. Take Western Digital model WD30EFRX. It has two revisions, 80.00A80 & 82.00A82. The 1st one is has a slightly wide speed variance up to 30MB/sec at the start of the drive but the 2nd revision has two distinct groupings which indicates that something changed between the two sets but no indication of which drive you got. This graph for a WD40EFRX is indicative of frequent drive failures as well as a fairly wide variance of possible speeds (and also looks like multiple groupings). The speed grouping could be the result of the storage controller it was attached to but I kinda doubt that.
  7. I've made some changes to the image search routine to make a log. If you still do not get any images, please comment with the time that you ran your scan (with time zone) so I can find your specific logs.
  8. With the latest updates, the plugin is fulfilling my needs nicely. I've verified the miss/hit logic and upon re-install of a Steam game, the download speeds were blistering.
  9. Not yet. I haven't had time to do so yet. Personal time on the PC has been limited of late. I'll post an update when it is.
  10. I see that in mine too, I'll investigate. I'm assuming the app works fine otherwise?
  11. Open a telnet prompt and type in "lshw -c disk" which will list most of the storage media attached. Look for your USB media. Mine looks like the following *-disk description: SCSI Disk product: USB Flash Drive vendor: Lexar physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: 1100 serial: AA00000000000489 size: 29GiB (32GB) capabilities: removable configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sda size: 29GiB (32GB) capabilities: partitioned partitioned:dos configuration: signature=c3072e18 Look at the size on both the disk & medium. If they match, your drive was mislabeled. If the Medium is smaller, than the entire device isn't partitioned to it.
  12. Hrm. Nothing stands out as being potentially invalid
  13. I don't suspect it is. The only information being passed is a list of vendors & model numbers. ETA: This got me thinking - what is the manufacture & model number of the drive displayed in the app?
  14. Thank you. For some reason, you are getting back basically an empty packet with no data. I'll need to add some debugging on my end that'll log the requests coming in and the responses. I'll reply to your email when it's done though I don't have an ETA for when it'll be ready as I'm getting married on the 27th at my home and we're doing basically everything 'cause of COVID-19.