بعد اطلاق النسخة التجريبية الأولى للفيجوال ستيديو 2010 في شهر ماي الفارط, تلقى عدة انتقادات من طرف المستخدمين له والضعف المشار إليه بشدة هو السرعة
حول هذه النقطة Rico Mariani أحد الأعضاء الأكثر تأثير في فريق المطورين يقول في مدونته أن
الmulti-threading كانت أحد مخاوفه الرئيسية
اقتباس…the product is a lot more multi-threaded than previous versions and in some cases synchronization between threads was less than great.
Weston Hutchins المسؤول على المشروع داخل الفريق يؤكد:
بالنسبة له ، فإن مشكلة السرعة تم حلها جزئيا ، وخصوصا عند بدء البرنامج.
ومع ذلك ، فإن الفيجوال ستوديو 2010 لا تزال في الوقت الحاضر أبطأ من النسخة 2008.
اقتباسWe've managed to trip around 30% of the startup time since Beta 1 but we still are slower than Visual Studio 2008. Part of the reason is that we are now bootstrapping the CLR which is causing an increase in the time. We're looking to further improve this number but it's unlikely we'll get to VS 2008 levels.
كيفية استخدام الذاكرة لزيادة وتحسين الأداء يجب أن يكون هو لب التحسينات في المستقبل.
Rico Mariani يعترف أيضا أنه يعمل على ذلك بالفعل.
يقدم تفاصيل أعماله المستقبلية في المشروع و التقدم المحرز فيه :
اقتباسMemory is of course the main issue and there are three main sources of bad consumption that are getting targeted:1. Managed images, especially ngen'd images. It's just super, super, simple to take a dependency on a whole DLL in the managed world when all you need is a tiny slice of
it. This has the lovely property that others then build on those DLLs creating a great big tree of unneededness. The good news is that examination can often lead to good refactoring opportunities which can save everyone a lot of memory. This is for sure the #1 issue.
2. Unshared, unmanaged Heaps. There are many low level pieces that manage their own memory and they inevitably do it with CreateHeap – joy. Of course they make their own nice giant heap ready to go and then put about 22 bytes in it. Multiply that by all the components that think they need their own private heap and it gets unpleasant awfully quick. Thankfully, this, too, is somewhat addressable. Interestingly managed memory use hasn't been a big problem other than it's fair share of leaks (see next)
3. Memory leaks, pretty much universally, can be a problem in a product the size of VS. No technology is immune but I sure like finding the managed ones better than the unmanaged – they literally can't hide. Other things that look like leaks but aren't really – it's important to use AddMemoryPressure/RemoveMemoryPressure to give the GC a chance to help you with your handle objects. VS has a lot of those.
وختاما ، بتفاؤل ، أن المنتج بالنسبة له بعد التحسينات بالفعل "أفضل بكثير".
لكن السؤال المطروح هل هو جيد فعلا ؟
مترجم من موقع developpez
