Michelle,
The way I see it you have 2 options. Typically the slow performance from Views is relative to a few things. The complexity of the data, the complexity of the query behind the view, or the geometry storage you are using. If using SQL Server there are some known issues with performance degradation when using ST_Geometry versus SDE_BINARY. So if you are using ST_Geometry I would expect there to be a little lag. So you could look at changing the geometry type being used to store the features.
Secondly, while stand alone feature classes sound like a drag it does not add too much overhead if it is scripted. I also ran into these same performance issues and to keep performance optimal I created a stand alone feature class from my view, then scripted a truncate and append method whereby I would truncate the stand alone feature class only if the record count in the view was more than 1 or 2 to ensure good data was in the view. Then I would append the records from the view to the stand alone feature class. Thereby breaking the join between the tables, increasing performance, and allowing me the opportunity to modify the spatial index if needed. Additionally if you have any attribute indexes on the feature class they will remain but might need to updated after a bulk load. If you are handy with python or model builder this could all be automated on a nightly routine after a recnpost or any other nightly maintenance. Furthermore, since using a truncate and append method there is no need for an exclusive schema lock to update the data, meaning ArcGIS Dekstop or Server could be using the data and it can still be updated while it is still in use so long as it is not versioned. The users might see the data disappear for a second while updating but if they pan or zoom it will come back. If doing this while no one is connected is an option then that is when I would recommend doing this, but in some cases you might need to update during the day just saying it could be done mid-day.
Glad to hear things might be moving along although I have heard differently from others about how soon this will be addressed, I will keep my fingers crossed thanks for the update.
