awasu.user wrote:Why [not]one API call?
Because Awasu has been written over a period of many years, and things that might make sense now maybe didn't back then
The idea was always to let information be extracted out of Awasu based on content
, not on structure e.g. "what stories are there about subject X within the past 3 days?", not "give me information based on how I've organized my feeds".
I'll see what I can do to add something to Awasu to give you what you want; the suggestions I gave earlier are ways to do what you want with Awasu as it is now
awasu.user wrote:General idea is use more RAM than Hard disk to this operation to protect HD from devastation.
I used to worry about SSD writes as well, but these days, SSD's are good enough that they are likely to outlast the rest of your computer and you don't really need to worry about it
The new build I'm going to send you soon will go a long way to reduce writes (it's search index updates that causing all this disk activity, and the new build reduces this).
One option you could really consider is to set up a RAM disk and run Awasu from that (I use DataRAM). Configure your data files to live in a specified directory
, and move your existing files (Local and Roaming data
) into that directory.
Then, when you want to run Awasu, copy those files to your RAM disk, point the DEBUG.INI file to the new files, and Awasu will run using those files. When you're done, copy the files back from the RAM disk to your SSD. Awasu will really fly if you do it like this
The only down-side is that if your PC crashes, you will lose those files on the RAM disk (although you will still have the ones on the disk, so you will only lost the work you've done since the last copy).
Edit: BTW, the DataRAM program has an option to save/load the contents of the RAM disk to a disk file, so you don't even have to worry about copying the Awasu data files around. If you're going to do things like this, you might also want to consider running Awasu in portable mode
, so that everything
is on the RAM disk, so that it's all self-contained (this also means you don't have to worry about things like absolute vs. relative file paths, what drive letter you mount the RAM disk on, etc.)