Thing is, many of these things were mitigated - quite a lot - with 0.6.2 version. It really shouldn't be taking so long.
Not for me...
When I start my 0.6.2 client after a single day off, the time to synchronize is considerable. The disk works frenetically.
I suspect indexation time is the issue here... does anyone know how the blockchain index is structured? If it is just a sorted disk array for example, inserting anything would be linear on the amount of data already there.
Plus, I believe it would help to do bulk inserts, asynchronously, if that's not done already. This would allow the download+verification to continue while indexation is processing a previous bulk. I have the impression that the whole process is synchronous (download a block, verify it, insert in BD, download next block, verify it, insert and so on...). If that's the case, it could be optimized. Not saying it's easy, but it's possible.