>>> I can see all the query messages in the status bar on the bottom of the screen (0 records in 1 sec here, 0 sec in 2.5 secs there, and so on).
>>
>>sounds like you need to take advantage of rushmore optimization on your underlying tables and setup some index tags that match the where clauses on SQL in the slower views.
>
>Dear, I have tags comming out of my ears. Could it be that some of these tables have an average of 60,000 records and one of them 160,000?
>
>Thanks!
>
>Alex

As long as you have set up table indexes and used them properly in the view, it shouldn't matter. One of our tables has ~1.75 million records and the view pops (relatively) quickly, < 2 seconds.

How many views do you have in each DE? I ask only because you mentioned getting multiple query messages at the bottom of your screen. You might consider using cdeLogicals for any lookup views, and again, only instantiate them when needed.