In my experience, sprint planning usually takes half a day for a two-week sprint on a complicated project with clients who don't really know what they're doing. Obviously, with a smart, experienced team it's usually quicker.
Sprint planning time doesn't scale linearly, though - a four-week sprint generally doesn't take a full day to plan and a one-week sprint will still take about the same amount of time as a two-week one.
Sprint reviews should only really take an hour or two; half a day at absolute maximum. Remember, you're demonstrating what you've built. Even Microsoft launching a new flavour of Windows doesn't run full-day demos - people switch off and get bored.
Your sprint retrospective should be something that your team does after everyone else has left. Consider it akin to sitting back with [coffee/beer/hard liquor of choice] and asking yourselves how you did. It's not supposed to be a formal, minuted discussion - rather, it's an opportunity to genuinely reflect on recent events. An hour maximum in my opinion, and usually closer to 20 minutes.