Any problem with leaving the DrivePool interface up all the time?

[Elijah_Baley]

I have everything set up and running quite well. It has been totally stable for at least the last year, maybe a bit longer. The computer I am using does nothing except Emby and DrivePool. I do all, well almost all, maintenance from a remote computer.

I was wondering if there is any downside to leaving the DrivePool interface active all the time so i do not have to wait the sometimes long time for it to load?

It does not matter much as that computer seems well over powered for its use and I have had no problems with it for at least the last year. I just am looking for ways to streamline my daily/weekly tasks and having the interface always up would be one step in the right direction. 

Thanks for any info. about this. 

[Shane]

I've left it open for days (and occasionally weeks) between remote sessions and not run into any issues. Only consideration I'd give is that I wouldn't necessarily trust Windows itself to keep behaving properly if not rebooted at least once a month, but that depends a lot on version, bloat, load, hardware, etc.

[Elijah_Baley]

17 minutes ago, Shane said:

I've left it open for days (and occasionally weeks) between remote sessions and not run into any issues. Only consideration I'd give is that I wouldn't necessarily trust Windows itself to keep behaving properly if not rebooted at least once a month, but that depends a lot on version, bloat, load, hardware, etc.

Thanks. I think my particular Windows 10 install on that computer is about as stable as any Windows 10 installation can be. That computer is also quite under-loaded and no really unusual software is used, except DrivePool itself. 

I am thinking it will be fine and I do reboot the whole setup at least monthly. 

I just REALLY need stability and ease in my life right now.

[Ac3M]

I ran into something strange. I swapped the pool with another computer running another pool, which in itself was weird as it automatically imported some one of the 3 pools into an existing one, without my permission. However, that's not the issue, but I never removed the software from the original computer and I'm using that, currently in Trial mode as I didn't see the point in using the license when I wasn't having any drives in a pool that didn't exist.

 

Anywhoo, my computer's been periodically strange and I think it was due to muppet cables for the drives (I'm using external SAS>SATA via SAS cables and custom built bacl plane PCBs with SATA for 2½ drives, so there are a lot of cables left & right), and the computer has been having other issues such as glitches with the PCIe NVMe SSD which has resulted in corrupted system files, and add also the regular crap that happens in Windows after updates. This installation has seen most problems for the past 2 years since it was installed (I think it's a personal record for my longest installed OS). I haven't had any viruses yet, and I hope I won't either.

So, the issue I encountered here was that I left the UI open for a remote session, I think 2 days ago, and I activated the Service Log a few hours ago and as I was scrolling up and down as I was looking for errors I noticed that it lagged like crazy.

It took 10-15 seconds between every jump at times. I have had similar lag issues via Windows Explorer (Network drives on the other pool computer) but I never thought the UI would do this since they're not really related in that sense.

I closed it and restarted it again, and it was running like new again, so I think there's something not properly flushed in the caching for the UI.

Could be an OS issue perhaps. My machine does have 136 GB of RAM and most are unused pretty much all the time, and I think I have the memory scrub function activated where all memory is scrubbed every 8 hour - Don't ask me how it works because I don't really know. It's a SuperMicro Motherboard with dual AMD Opteron 6378 Processors @2.40 GHz and 16 cores so it's a beast but not very fast I/O as it only got PCIe v2.0, and I think this is something proprietary for SuperMicro but I could be mistaken since I don't have much experience with servers and workstations of this caliber.