Hi!
This doesn't work at all. I have to kill off the app's processes.

Space radar starts scanning my disk and periodically refreshing the on-screen image while saying "Scanning, try grabbing a drink". When done, everything disappears and I'm faced with a blank window, only the window controls (close, minimise, maximise) show.

Mac OS X 10.11.3
256GB SSD

Try Photon as recommended by @kidwm
https://twitter.com/kidwm/status/655947033950351360

First off, I want to say that I really like the UI, it's actually pretty similar to the disk scanner tool I currently use. So when I found this project and saw in the README that you were looking for feedback from Windows users, I thought I'd give you my first impressions.
Note this analysis only pertains to v3.3.0, as there currently isn't a windows version of the pre-release .

• As you can see in the screenshot below, the text that is supposed to be in the middle is a little off-centered.
• When compared to the images in the README, it also seems like the graph colors are appearing differently.
• To analyze my whole root directory the program took about 3.5 minutes, which is a bit slow, but it appears that you plan to address performance issues in an upcoming release.
• I would prefer if the program could also display the remaining empty portion of the drive as a part of the graph.
• It would also be nice to have the graph scale with the size of its containing window, because when I first launched the application the window only displayed about 80% of the overall graph and needed to be adjusted.

Overall, I think this project has a lot of potential, so feel free to let me know if any of my points need clarification or you need someone to test future builds. 👍

which are required so that it doesnt spend 4 hours scanning my entire 10tb google drive

I'm interested in using space-radar to view data from a remote server. That feature does not appear to be in any of the release versions, so I've tried to build from master. I know next to nothing about electron or the node ecosystem....

I'm on a Mac running OS X 10.11.2

I cloned the repo, ran npm install electron-packager --save-dev, then npm run build. The resulting .app does this when I run it:

npm install electron and then npm run app does this:

hartzelg-UXG8WL:space-radar hartzelg$ npm run app

> [email protected] app /Users/hartzelg/tmp/space-radar
> electron .

App threw an error during load
Error: Cannot find module 'app'
    at Module._resolveFilename (module.js:455:15)
    at Function.Module._resolveFilename (/Users/hartzelg/tmp/space-radar/node_modules/electron/dist/Electron.app/Contents/Resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/hartzelg/tmp/space-radar/main.js:4:11)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
^C

and after npm install standard, running npm run test complains vociferously.

Can you share instructions on how to make this work?

Or, can you release (preview release?) a version that includes the "read data from file" functionality?

Thanks!

After various testing on speeding up scanning the disk, I'm settling with simply using the node.js async FS methods. However, running the disk intensive methods seems to starve the libuv event loop a little way that even setIntervals seems to be heavily delayed. What's worse the experience of running electron's renderer process while readDirs would seem like the UI has became unresponsive.

My current approach (#5) to that is to run disk scanning in separate (headless) renderer process (either spawn from browser or remote). However, for the target UI process to receive data, the disk scanning processing would need to send messages as an electron IPC method. The scan disk process would send the browser (main.js) an IPC message, and the browser would send the UI process another IPC method. At the expense of more responsive UI overall, it seems the overheads are the price to pay for message passing, and the UI would still seem to freeze marshalling a large json.

One of my favourite hacks for doing message passing on the web is abusing localStorage. LocalStorage is usually pretty performant and allows multiple pages to listen for localStorage change events and that allows me to write a simple localStorage IPC mechanism. Without any benchmarks, this would be faster than electron's IPC in theory (since it would be serialize once instead of twice), and it feels faster than with electron's IPC (yes, feeling is subjective and bad for actually measuring performance).

There's a catch with localStorage, because there're limits associated with how large a string you could write to it. "Uncaught QuotaExceededError: Failed to set the 'lsipc' property on 'Storage': Setting the value of 'lsipc' exceeded the quota."

A simple workaround for now is simply to fallback to electron's IPC calls when localStorage throws me an error (see #7). However even electron IPC has it limits when I start getting [50582:1023/134245:ERROR:ipc_channel_reader.cc(65)] IPC message is too big in my logs.

What other choices do we have? Right out at the top of my mind is the following

1. IndexedDB
2. Web Workers
3. Service Workers
4. JSON Streaming
5. Message Chunks

IndexedDB seems like a natural upgrade for localStorage. I haven't use that, but it seems like the next natural path to take. Web Workers could be a lighter form of spawning a headless process, but doing require('fs') in a Web Worker seems like a no-no for now. Which then the next better thing would be to try service workers.

Apart from trying to incase the amount of data that can be transferred, the existing size limitation could be overcome is messages were sent in chunks. One way is perhaps to send diffs for updating in a way a streaming JSONParser could recreate the JSON message entirely.

Lastly, the simplest UI hack would be actually how I think most scanning applications does that. Simply not do anything or show a progress bar until the entire scanning is done (then the disk scanning could be done in the same process).

VS does not open the project.
How I can build the app fro Windows, Linux, Mac?
Thank you

I see from packages.json that this project is MIT licensed. It's not immediately apparent what the license is when first looking at the project, and not everyone will know to check in packages.json. Having a LICENSE file in the repo that contains the full text of the license would make it much easier to find out how the project is licensed.

Thanks much, and apologies for being such a nit-picky nerd :)

Seems like this feature is broken. Nothing happens. No scanning starts, no error is raised, nothing.

GetSubVisual() result is empty object if mesh contain more than one submesh.
If mesh contain only 1 submesh this function working properly.

I have a textfile input with ~330K entries; I've let space-radar run for several hours, but it doesn't seem to be doing anything.

Hello
Very impressive tool!!!
Do you think it would be easy for me to make it work with cloud services like dropbox, FTP, ...
I would use @JbIPS 's https://github.com/silexlabs/unifile/ nodejs lib
Thx

It would be cool to be able to delete files directly from space radar's interface. It's a good tool to quickly locate files that could free up space if deleted. Adding that possibility would speed up that workflow.

Requires a vibrant app icon to distinguish itself from other apps, especially when switching apps 😛

Usefull with context menu

the title says it all :)

TODO

Visualizations

• Flame Graphs (Added v5)
• Color coding
• Display list of items (Added v5)

Optimizations

• Canvas Graph Donut Rendering
• Webgl TreeMaps
• More efficient memory structure
• Collapse too small items

Functionality

• Export DU file
• Watch directory structure

Releases

• Bump electron builds (Added v5)
• Windows builds (Added v5)
• Linux builds (Added v5)
• Fix Automatic Mac Builds
• Try Electron builder

• Animations for Treemaps
• Kill Processes
• Filter / Search files
• Tweak Graph Colors
• Free space and estimate scanning
• Incremental Updates
• Side panel
• Treemaps WebGL Rendering
• Decide whether to use FlatBuffers, CaptnProto, custom data structure or implement some streaming interfaces

DU file import

• Read-only Mode
• Allow STDIN / allow loading as a parameter
• Remove button and add Menu Item
• Add Linux builds

Hi,
In some cases I find that the size of a child ring is very disproportionate to its relative amount of space.

For instance, I have a folder "Run16" of size 33.50 Gb (figure 1) and it has many sub-directories. One of them is called "vpd_slew" with a size of 23.88 Gb (figure 2). Even though this is 71% of the space (reported as 36%) it shows up as a tiny almost invisible sliver.

Let me know if I can provide more useful info. SpaceRadar is great, thanks for good work.

I love that you have included the Box-View now, but it could be improved style-wise. Right now it looks to gray. I would like some styling similar to Grand Perspective.

When using multiple displays, it's not possible to move the Window around the screen, nor move it to another display.

I wanted to try the tool but vesion 4.4.0 is not for Windows. Only for mac. Version 3.3.0 is vor Windows.
Please make it available for Windows too.

Thx

I'm not able to open a size file from the UI.
Did I miss something macroscopic?

I'm pretty this is my issue but after looking through readme and release notes I'm nost sure how to resolve it and I'm using Windows 10 64x Home Edition.
I downloaded, unzipped and ran npm install on space-radar-4.4.0.zip.
During the npm install I received this error:
Cloning into bare repository 'path\git-github-com-experiments-photon-git-{guid}
Warning: Permanently add 'github, {IP}' (RSA) to the list of known hosts
Permission denied (publickey)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Open finder or explorer to destination

One of the known issues with keeping file system objects in memory is that that v8 heap memory grows towards a limit (~2GB max) with increased CPU usage as garbage collection becomes more expensive.

I've started looking into using different approaches of solving the problem, including using native libs (eg. hashset) and embed databases (sqlite, leveldb, lmdb, ejdb), and with each approach comes its own set of advantages and drawbacks.

Co-incidentally, there's has been some interesting discussion on disk visualization tools on hacker news and led me to find out about other work with regards to dealing with performance and huge number of files. In particularly,

http://duc.zevv.nl/
https://github.com/jarun/nnn/wiki/performance-factors
zevv/duc#161

I'm using space-radar on a Mac. When I right-click on a directory, the "open" option is grayed out. I suggest that this menu option should work the same way as "open" on a command line - that it should launch Finder on the directory. That's the interface most familiar to a new user. (I suppose the corresponding tool under Windows would be the Windows Explorer).

I would also like the option to open a terminal window in the directory, since for an experienced user there are many actions that are easier from the command line.

On Mac, use San Francisco for newer OS with fallback Helvetica Neue. On Windows, Segoe UI. And so on for other OS.

Relevant articles:

• http://furbo.org/2015/07/09/i-left-my-system-fonts-in-san-francisco/
• https://medium.com/@mwichary/system-shock-6b1dc6d6596f

Seems to be a popular feature request from my friends (including @cheeaun)

I was looking at some of my past conversations with @kig and realized that he has done pretty cool diskspace visualization in the past and one could always borrow/steal ideas 😂

http://fhtr.org/wfsv/
http://fhtr.org/projects.html

Filezoo - a minimalistic zoomable file manager
http://github.com/kig/filezoo
https://www.youtube.com/watch?v=itsOMpMpPto

Also https://tabletree.io/

I suggest assigning colors as follows:
For files, use the same colors as GNU ls by respecting the environment variable LS_COLORS. If that variable is not set, then use the defaults printed by "dircolors -p".
For directories:
For .git, foo.git, .svn, and other configuration management directories: use the same color as for a .tar file.
For .../bin, /Applications, etc: same as an executable, or a .exe file.
For ~/Pictures: same as a .jpg file.
Otherwise, a directory should inherit the color of the contents, with votes weighted by space. I.e., add up the space for all the green files & subdirectories, all the red files & subdirectories, etc. Whichever color accounts for the most space is assigned to the directory.

Coloring by content would make it easier to spot duplicate collections of files, because those directories would be assigned the same color. To make this even easier, one could construct a directory color by averaging over the color of its contents. However, I suggest this be an option rather than the default.

version 5.1.0 actually claims to be version 1.7.8 when selected in the Finder

Looks nice on the videos, but as far as I can tell this does not work on Mac Sierra (10.12.6). If I scan the disk or a folder or add a du file it always just displays "Refreshing..." (tried two separate Macs). During the scan I can see the "Scanning..." window and it seems to get stuck on a file. I tried earlier versions too (5, 4.4, etc).