none
m.trends slow down RRS feed

Answers

  • We have a fix in the queue for these long threads.  http://tst.social.technet.microsoft.com/Forums/en-US/ieitprocurrentver/thread/7e4156be-590d-42df-b393-dc95160cb2ff/ (data is a couple weeks old though, but you get the idea hopefully). We hope to deploy a fix on 2/2.

    That being said I really don't know why any thread should ever need more than 40 replies. If an issue can't be resolved by then I'm not sure additional replies will help. If people just want to pile onto an issue, we should implement a 'join question' feature like answers has.


    Community Forums Program Manager
    Friday, January 20, 2012 7:32 AM
    Answerer
  • > That being said I really don't know why any thread should ever need more than 40 replies

    I sympathize with Susan on the slow-opening issue. I'm seeing it on well less than forty posts too.

    However I agree with Brent that in the vast majority of cases any thread reaching 40 tends to be a thread where people have "piled on" to an issue and it is typically worthwhile locking the thread and starting again.

    These long threads typically

    - have lost their focus long ago with new questions asked in the thread irresepective of whether the original question was answered or not.

    - tend to have been started several years earlier so the OP is maybe asking about the original RTM product rather than the present SP2 / SP3 version of the product that people are having problems with today.

    - include several posts which say little more than "I am having the same problem" and which give little or no (mostly no) extra information.

     

    Aside (opposite situation): There is also a case for threads of a certain age (say from 2008, 2007 - so over 3 years old) to be automatically deleted by the system if they have had no reply since (note: "reply" not "answer" - i.e. the thread consists of a single post). The OP has long gone and his problem with him/her.

     


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Friday, January 20, 2012 9:16 AM

All replies

  • HI Susan !

    I think this issue has already been reported to Microsoft Forum Administrators. Issue is related to thread which have more than 30 posts approx. this can be lesser as well but the java script slows down the rendering. If you try to load the page without Signing In the Forums thread will load much quicker.

    Hopefully Microsoft guys will resolve this soon.

    Alternate would be, lock that thread and start a new thread linking to old thread and start new posts their.


    Please let me know if this doesn’t work for you. Hope I have answered you correctly.

    Thanks, Hasham


    Friday, January 20, 2012 6:26 AM
    Moderator
  • When you are trying to answer a post, not signing in is not an option :-)

    I'm not a moderator for that forum, and I'm not sure I like locking posts when the person is having the same issue and googling and then hitting a thread where the issue isn't resolved.

    I'd like to see an thread in a fully resolved condition before something is locked.

    Friday, January 20, 2012 6:29 AM
  • We have a fix in the queue for these long threads.  http://tst.social.technet.microsoft.com/Forums/en-US/ieitprocurrentver/thread/7e4156be-590d-42df-b393-dc95160cb2ff/ (data is a couple weeks old though, but you get the idea hopefully). We hope to deploy a fix on 2/2.

    That being said I really don't know why any thread should ever need more than 40 replies. If an issue can't be resolved by then I'm not sure additional replies will help. If people just want to pile onto an issue, we should implement a 'join question' feature like answers has.


    Community Forums Program Manager
    Friday, January 20, 2012 7:32 AM
    Answerer
  • I've had Outlook 2007 mailto bugs turn into an Outlook 2010 mailto bug and I've had to go back on old threads begging people to open up support cases.  When you have an issue that is seen by multiple people, and it's an update or patching related, it's reasonable.

    Friday, January 20, 2012 7:55 AM
  • > That being said I really don't know why any thread should ever need more than 40 replies

    I sympathize with Susan on the slow-opening issue. I'm seeing it on well less than forty posts too.

    However I agree with Brent that in the vast majority of cases any thread reaching 40 tends to be a thread where people have "piled on" to an issue and it is typically worthwhile locking the thread and starting again.

    These long threads typically

    - have lost their focus long ago with new questions asked in the thread irresepective of whether the original question was answered or not.

    - tend to have been started several years earlier so the OP is maybe asking about the original RTM product rather than the present SP2 / SP3 version of the product that people are having problems with today.

    - include several posts which say little more than "I am having the same problem" and which give little or no (mostly no) extra information.

     

    Aside (opposite situation): There is also a case for threads of a certain age (say from 2008, 2007 - so over 3 years old) to be automatically deleted by the system if they have had no reply since (note: "reply" not "answer" - i.e. the thread consists of a single post). The OP has long gone and his problem with him/her.

     


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Friday, January 20, 2012 9:16 AM
  • I'm not a moderator in anything but the SBS forum.  Therefore, I do not have the power to lock a thread.  In these areas where I've got threads that I go back to to help people due to patching issues, I'd honestly prefer that they are in one place and not scattered all over the place.  When I need a head count of issues, I don't need a locked post.

    If someone still needs help on that thread and the post is locked, it makes people angry.

    The forums are not healthy enough yet to be culling old posts that are not flagged as answered.  People have not been trained to flag yet.

    Friday, January 20, 2012 2:14 PM
  • > The forums are not healthy enough yet to be culling old posts that are not flagged as answered. People have not been trained to flag yet.

    I agree.  Please read my post again - there was nothing there about not flagged as answered.

    My suggestion was restricted only to (very old) threads that only contained a single post with therefore no replies at all for several years. Removing them hurts nobody.

    (and stops people from years later "replying" with "I have a similar problem" when they should be starting a new thread)

    -----------------

    > I'm not a moderator in anything but the SBS forum. Therefore, I do not have the power to lock a thread.

    If you don't have the power to lock threads in the SBS forum that's very odd. I can lock threads both when in the TechNet forums and when in the MSDN forums provided I am a Moderator in the particular forum (and as far as I can remember the SBS forums are either in TechNet or MSDN forums).


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters

    Friday, January 20, 2012 2:19 PM
  • We have a fix in the queue for these long threads. 

    Did the proposed fix get rolled out?

    It's possible long thread performance is better, but it's not hard to find one that locks IE9 up still, even on a good computer. 

    It used to take about 100 posts.  Now it seems to be higher - only incrementally better.  I haven't done any objective measurements, but the problem threshold only seems to have been moved, so that it just takes an even longer thread to lock things up.  Don't get me wrong, that's great, but couldn't the problem actually be fixed?

    As an example, a 413 post thread that still locks up the browser for a significant time:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/09fd46ff-65f1-4fa7-ae2d-9f3b2644fad6#9a07de4c-eaa2-4c07-8604-3ba0f1b2a7ab

    -Noel


    Detailed how-to in my new eBook: Configure The Windows 7 "To Work" Options

    Thursday, February 9, 2012 6:20 PM