I have a massive problem using oneswarm with firefox. Firefox which usually always sucks up quite a bit memory by itself becomes almost unusable for me.
What if you intergrated azures to a stand alone one swarm client. Wouldn't you be able to push down cpu and memory usage this way?
Standalone client to speed things up.
(10 posts) (5 voices)-
Posted 4 years ago #
-
I agree on that. I also experience great difficulties with both firefox and opera. Of some reason the web interface makes the browser cache huge amounts of data and many functions like listing torrents and searching, often hangs the interface. Also when I have the web interface open the browser process pushes my CPU usage up to 100% on the CPU core it's residing.
If the GUI could be stripped out of oneswarm completely that would be the best because then stand-alone clients could be written to it (both regular GUI and CLI). The second best would be to rewrite the Vuze GUI to implement all oneswarm features.
I think the web interface is ok for now (at least there is an interface) but as oneswarm becomes stable some day in the future I don't think it's the way to go, it's to resource consuming and unneeded (why a web interface at all from the beginning? Java is already platform independent.).
Posted 4 years ago # -
I think it's nice to have a web interface that you can access from anywhere. Especially if you run it on a headless server.
But sure, an effective C++ version of the server and GUI would be nice..
Posted 4 years ago # -
I'd like that too. Would be nice to have a version with rtorrent as backbone and only commandline to get some dedicated nodes up. But until then, thanks for all the work devs.
PS. Looked through the source a little but I'm just too lazy. Sorry ;S
Posted 4 years ago # -
>I think it's nice to have a web interface that you can access from anywhere. Especially if you run >it on a headless server.
Web interface might have a point if accessing remotely but I would say that SSH makes it quite unnecesary (at least for Mac and Linux where setting up a X-forwarding SSH-server isn't a pain in the ass).
Anyway I see web interface as a bonus feature not the default interface.
I'm not skilled enough to navigate the source of oneswarm myself. Is there anybody here who knows how hard it would be to separate the GUI from the backend?
Posted 4 years ago # -
Since my server is headless i don't have X on it. (X takes unnecessary resources for a server)
Posted 4 years ago # -
Well, X is only run at the client if you do X-forwarding, that's the point with it.
Posted 4 years ago # -
Yeah, you are right. Maybe it won't add so much, but i have to rebuild some libraries and such for X support.
Posted 4 years ago # -
Seems we don't have to worry about that now. One of the planned features is "Headless (no X on linux) support" (http://wiki.oneswarm.org/index.php/Version_0.7).
Posted 4 years ago # -
Prism could also be used instead of the main browser (usually Firefox/IE)!
http://prism.mozilla.com/
It's multi-platform too!Posted 3 years ago #
Reply
You must log in to post.