Oh no just, serialization as in "I'm using serialization (XStream XML serializer) which is a cpu bound task", that's all I meant.
Although perhaps there is an interesting problem here: I'm using MapDB, an embedded database that has never once caused me IO related headaches (blocking indefinately while it waits for file handles, etc). Thus I consider "serializing to mapdb" to be a CPU bound task. Is this fair? Technically its opening and writing to file streams, should I consider it an IO task and use the IO pool which, IIRC, will attempt to pull up another thread for me?