• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

FFS Microsoft

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #71
    Yes, in theory generics should be as good as making copies of same code with explicit types - just like what I did, in practice generics seem closer, but I want to have 1.1 build for Mono, plus, AFAIK same issue of sorting may apply - have you reflected generic sorting code to see if they can also fall back to slow generic array sorter? I've found at least one bug in .NET 2.0 sorting related to huge performance penalty in some cases that worked just fine in 1.1.

    Comment


      #72
      Originally posted by AtW
      No, and I am a lot better technologically than dotLucene - its not scalable for multi-billion page indices, I've got 1 bln pages now, and plan to add many more in a couple of months, which is why I am profiling code to make sure its fast.
      I've run 610 million documents with 20 attributes ~ 79Gb index and I'm getting response times on lucene around 450ms. Not great but not too bad.

      At least you're getting to deal with fun amounts of data
      Serving religion with the contempt it deserves...

      Comment


        #73
        Originally posted by AtW
        Yes, in theory generics should be as good as making copies of same code with explicit types - just like what I did, in practice generics seem closer, but I want to have 1.1 build for Mono, plus, AFAIK same issue of sorting may apply - have you reflected generic sorting code to see if they can also fall back to slow generic array sorter? I've found at least one bug in .NET 2.0 sorting related to huge performance penalty in some cases that worked just fine in 1.1.
        Use GMCS2 compiler and you can have generics for mono
        Serving religion with the contempt it deserves...

        Comment


          #74
          YAWN. Shouldn't this be in technical?
          I am not qualified to give the above advice!

          The original point and click interface by
          Smith and Wesson.

          Step back, have a think and adjust my own own attitude from time to time

          Comment


            #75
            The whole of .NET was written by one guy named Rashish in India.

            If you have anything to say, you can contact him on rashish@hotmail.com

            HTH

            Comment


              #76
              I want to avoid explicit 2.0, even though my main build is done for 2.0, but 1.1 build is needed for profiler to work well - for some reasons it hungs in one place when build is 2.0.

              Originally posted by The Lone Gunman
              YAWN. Shouldn't this be in technical?
              No, because its a rant

              Comment


                #77
                Not tried profiling in 2.0 - still using legacy crap
                Serving religion with the contempt it deserves...

                Comment


                  #78
                  1.1 is stable enough, and 2.0 had some subtle garbage collector changes that I ranted about some months ago. But VS 2005 is much nice IDE

                  Comment


                    #79
                    Originally posted by AtW
                    1.1 is stable enough, and 2.0 had some subtle garbage collector changes that I ranted about some months ago. But VS 2005 is much nice IDE
                    So AtW knows better than Microsoft. One the one hand we have the largest company in the world which has made multi-billonaires of its founders and on the other we have AtW who has made fu*k all.

                    Hey AtW have you thought of going through all of MS software and removing all their error checking and abstraction. You will really speed things up in places and you could submit the changes as bug reports to MS.

                    Comment


                      #80
                      Wocky - go look at something shiny for a moment.

                      Comment

                      Working...
                      X