handles and computer performance

[pelegk2]

1)what are execlly handels?
2)if i have a software on aserver,which i se that hold say 100,000 handels or more does this effect the server performance?how can i check it? did any one read an article about this issue?


thnaks in advance
peleg

[TheCPUWizard]

1) A Handle is something (completely undefined as to content) that allows something else to reference something.

2) The number of handles has little to do with performance. Assuming you are running Windows, start with using PerfMon.

[Fireseed]

In fact, A Handle is a system pointer. You should not worried about performance impact of Handle on system performance

[TheCPUWizard]

In fact, A Handle is a system pointer. You should not worried about performance impact of Handle on system performance

Handles are NOT (necessarily) pointers. They can be many things (some are indices into an array, some are simply timestamps, others are internal undocumented values).

[Fireseed]

Handles are NOT (necessarily) pointers. They can be many things (some are indices into an array, some are simply timestamps, others are internal undocumented values).

Handle isn't a simple point on significance, whereas it is used as a point in code.
you may see following in winnt.h

typedef void *HANDLE;

[ajaywinds]

If your application is a long running application, then handle leak is serious problem. In Windows if the handle count exceeds above a certain limit( not sure about the exact limit count ), there is a big possibility of application crash. So better to avoid the handle leak.

[TheCPUWizard]

If your application is a long running application, then handle leak is serious problem. In Windows if the handle count exceeds above a certain limit( not sure about the exact limit count ), there is a big possibility of application crash. So better to avoid the handle leak.

1) There is a difference between a leak, and valid usage [the post indicates NOTHING about leaks]

2) There is no overcall count or limit. Certain types of RESOURCES have limits, but that is a totally different issue.

So I fail to see what your post contributes to the actual situation that has been described, other than a statement of the obvious in a general way.

[Paul McKenzie]

Handle isn't a simple point on significance, whereas it is used as a point in code.

I don't know what all that means. A "handle" is just an informal way to specify some value type that the user uses in a program. It really has no definite meaning. For example, file handles, image handles, they could be pointers, structs, typedefs, or anything the author wishes them to be.

Regards,

Paul McKenzie