What does the long database operation have to do with the membership provider specifically? Does a long database operation have to run in order to determine identity or authorization?
I'm guessing a membership table containing millions of rows but without an index. Ouch.
SELECT operations used on typical page requests should execute in under 10ms or so - any longer and you've either got a complicated query (time to de-normalise) or missing something obvious (like an index).