Discussions

DigitalDud wrote:

So there's a number of well-known performance issues with .NET.  Reflection is slow.  Throwing exceptions takes half a second.  Cold starts take forever, the memory footprint is high.  Half these performance bugs people just take for granted, "Oh yeah don't use reflection a lot, its pretty slow". But WHY is reflection slow?  Why doesn't someone at MS open a bug against .NET, "Priority 1, fix NOW, millions of customers experiencing millions of dollars lost in operating costs cause of a slow reflection code, blah blah"

Well with the things you mentioned it's likely not to be performance issues. Its simply design issues. And as you wrote these have been VERY well documented and are widely known. If you have Exceptions in your normal execution path its simply plain wrong.
Moreover as these were design choices they are
a) likely to not be correctable without changing the design
b) speeding them up would not help anybody, because nobody uses these constructs in performance-critical code anyways.

DigitalDud wrote:


Environments like .NET are supposedly awesome because if you make performance improvements to the runtime, the JIT compiler, etc., every single program that targets .NET receives a performance benefit.  And today that is A LOT of programs.  But the thing is, they DON'T update the runtime.  They haven't touched it in years, and 2.0 didn't do much for performance anyway.  And it's not like you can't make runtime changes without breaking compatibility.  You don't have to touch the libraries, just make the compiler faster.

I'm here with you for this one (mostly). Obviously not the compiler, but the JIT-results, but I guess thats what you meant anyways.
E.g. why do NGEN compiled programs usually still perform worse that the same application compiled with an optimizing c++ compiler?
With the additionaly system information that NGEN has (Exact processor type, available RAM, ...). It should always be able to outperform or at least be on line with precompilers.
And the JIT still isn't able to take advantage from its special execution semantics to dynamically optimize applications (e.g. like HotSpot).

Theatronics wrote:



p.s.
Example of some Java I am trying to change to .. something else.

// Grab a pixel from an image.
 public int[] getRGB( BufferedImage image, int x, int y, int width, int height, int[] pixels ) {
  int type = image.getType();
  if ( type == BufferedImage.TYPE_INT_ARGB || type == BufferedImage.TYPE_INT_RGB )
   return (int [])image.getRaster().getDataElements( x, y, width, height, pixels );
  return image.getRGB( x, y, width, height, pixels, 0, width );
  }

In C#:

Image.GetPixel (int x, int y)

Theatronics wrote:


//Change a pixel in an image.
 public void setRGB( BufferedImage image, int x, int y, int width, int height, int[] pixels ) {
  int type = image.getType();
  if ( type == BufferedImage.TYPE_INT_ARGB || type == BufferedImage.TYPE_INT_RGB )
   image.getRaster().setDataElements( x, y, width, height, pixels );
  else
   image.setRGB( x, y, width, height, pixels, 0, width );
  }

In C#:

Image.SetPixel (int x, int y, Color color)

BTW: The java-code is bugged because there are other possible types than argb and rgb

steve, I think you are heading into the wrong direction.
As has been said Attributes are *META*Data. If you want to have a default value that is used in the program itself for something directly related to other settings its just other data and not metadata.
A simple way to set a default would be to simply add a readonly virtual property providing the value.

karnokd wrote:

Hi!
Can someone explain me, that in Windows (XP, Vista) when I insert a CD/DVD, the Explorer freezes for a couple of seconds and sometimes my mouse too? Maybe someone from the kernel or device driver guys knows the reason?

This has nothing to do with the kernel or drivers.
Windows Applications (this likely has nothing to do with Windows itself) have always been VERY WEAK in terms of asynchronious IO usage.
Just open a lage File in Notepad and it will hang until the file is opened. Or try some network access from explorer while the network is not yet available (e.g. pre DHCP) and it will hang until timeout and so on and so forth...

Could we just delete that stupid trolling crap from corona_coder? It's seriously off-topic. (BTW. I have an USB-mouse that reproduceable is able to kill/hang most Linux installations simply by plugging it in)

And I'm still interested to hear if somebody from MS is looking into this, because this IS a huge problem (at least for me)!
Moreover I'm still looking for somebody with the same motherboard to tell whether it runs or not!

Sven Groot wrote:



Foxfire wrote: The HDD did not break, it was a DVD and the graphics-card. The HDD just does these funny noises (EVERY time you shut off), but it didn't break.

Did you by any chance install nVidia's new SATA drivers? I installed those drivers a few days ago and got the exact same symptoms (funny noises when shutting down the HDD).

I rolled back to the drivers included in Vista and the noises went away.

I just couldn't resist and tried it today (the rollback) and it now the funny noises are gone for me, too. So obviously something wrong with the Nvidia drivers for the NForce4Ultra chipset.

However it did not solve the problem of shutting down the screen and then sitting for about 15 sec before it finally shuts down (though I got the feeling the timespan got shorter)

Yes, I did install the drivers. But if I remember right, the actual damaging was before installing the drivers.

The HDD did not break, it was a DVD and the graphics-card. The HDD just does these funny noises (EVERY time you shut off), but it didn't break.

And with the reasons above I don't believe that there is actually a hardware defect in either the PSU nor the motherboard. Of course this is possible, but imho the facts show more chance towards a general incompatibility.

Does anybody have this motherboard (and perhaps a similar setup) and could tell if it works without any pauses at shutdown with Vista??

cescotto wrote:

Are you sure this is not a PSU problem? Maybe your PSU has problems that combined with Vista's new power settings and a motherboard with a buggy ACPI implementation could have damaged the components.

Thats one of the first things that seem to make sense to me. It would even possibly explain the simultanious death of the graphics-card and the drive.

The situation could have been:
Say Vista sends some ACPI commands to power the devices down at shutdown. Something doesn't work and the devices immediately power up again and Vista immediately tries to power them down again. (Can't explain why this happenes exactly three times ?)
It could just be that the graphics card did not survive that fast and repeated powerup/powerdown sequence. And the other drive might not have died because there was no CD inserted at that time, so it did not have to (mechanically) spin up.

So the big question would remain: Is this a defect of the Motherboard (which seems unlikely to be due to the facts that
a) It did never have any issues with either XP, nor with any Linuxes
b) I did update the bios firmware, but it did not change anything. Afaik most parts of the ACPI interfaces are "handled" there, so this seems unlikely

or is it a general incompatibility of Vista (and its ACPI-Interface) with this hardware (combination) - in that case MS should warn or/and prevent Vista installs on that hardware.

It would be really nice to hear something from MS about this issue.