OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Dima202 on May 30, 2006, 02:06:01 pm

Title: Swap
Post by: Dima202 on May 30, 2006, 02:06:01 pm
Hello,
I just read the following faq:
http://mail.pdaxrom.org/node/29 (http://mail.pdaxrom.org/node/29)
Quote
The best solution is to store the swap on a CF microdrive or use it over the network (this can be really slow!).
Did anyone find a way to use swap over network which would work well?
I think that if I could use swap from my main machine which has a SATAII hdd over Wireless B(4.5 Mbps)... It should be much faster then SD(50kb/s?) or CF(??kb/s).

What do you guys think?  
-Also for this, I will not make my sd/cf suffer!
Title: Swap
Post by: GadgetGuy on May 30, 2006, 03:58:44 pm
Quote
Hello,
I just read the following faq:
http://mail.pdaxrom.org/node/29 (http://mail.pdaxrom.org/node/29)
Quote
The best solution is to store the swap on a CF microdrive or use it over the network (this can be really slow!).
Did anyone find a way to use swap over network which would work well?
I think that if I could use swap from my main machine which has a SATAII hdd over Wireless B(4.5 Mbps)... It should be much faster then SD(50kb/s?) or CF(??kb/s).

What do you guys think?  
-Also for this, I will not make my sd/cf suffer!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129001\"][{POST_SNAPBACK}][/a][/div]

I would use a fast CF card. CF cards are not very expensive these days - so if it dies, you can just get a new one. I am pretty sure that would be faster then using a network swap file... And for sure it would use less power than if you were to use your wifi card all the time....
Title: Swap
Post by: bluedevils on May 30, 2006, 04:42:51 pm
maybe I don't know the full story here, but wouldn't swap over the network be unstable?  You are relying on a wireless network for a system resource.
Title: Swap
Post by: adf on May 30, 2006, 04:49:00 pm
Quote
maybe I don't know the full story here, but wouldn't swap over the network be unstable?  You are relying on a wireless network for a system resource.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129038\"][{POST_SNAPBACK}][/a][/div]
I was wondering more what would happen if he took it away from home....swap though an internet cafe connection, or via bluetooth to a cellphone doesn't sound very hopeful
Title: Swap
Post by: bluedevils on May 30, 2006, 04:54:58 pm
believe me, a bt cellphone connection is not very stable or close to being fast enough.
Title: Swap
Post by: pgas on May 31, 2006, 01:33:12 am
you can use swap over nfs by tricking linux

http://www.denx.de/wiki/DULG/SwappingOverNFS (http://www.denx.de/wiki/DULG/SwappingOverNFS)

I used this for compilations without problem.
Title: Swap
Post by: ced on May 31, 2006, 03:37:13 am
I've used this in the past with kernel 2.4 and 2 weeks ago with the kernel 2.6 from OE --> NBD (http://nbd.sourceforge.net/)

It works really nice with my compact flash network card... in term of performance it's fine I don't see any issue... :-)
Title: Swap
Post by: Dima202 on May 31, 2006, 02:30:45 pm
Quote
in term of performance it's fine
Is it any quicker then using cf/sd?
Title: Swap
Post by: Meanie on June 03, 2006, 06:25:44 am
Quote
Quote
in term of performance it's fine
Is it any quicker then using cf/sd?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129177\"][{POST_SNAPBACK}][/a][/div]

let me put it this way. would you put your windows pagefile on the local machine or on another machine over the network?
just put your swapfile on a cf. cf is faster than sd.

the important thing here is, what is your swap needed for? if you need it to supplement memory to run heavy applications, then you want it to be as fast as possible and located locally.

if you need it for large compiles then having an additionsal swap for such purposes may be appropriate since speed is obviously not a major concern for you (otherwise you would be cross compiling anyway and not using the z to compile natively).

you can always have several swap files, one smaller one locally anbd a large one remotely. ust make sure you make the priority of the local one higher than the remote one so it will always use your local one first and only resort to the remote one when you really need it.