I'm not sure if I can answer all your questions, but I will try:
I have some questions regarding restarting QV Services.
In QV Server, qvs.exe is taking up all the memory, and my goal is to release the memory on the QlikView server.
Which version are you using? There was an issue with some realeases of QVS 9. If I remember correctly it was QVS 9 SR2.
First question, how is server memory used when end users connect to QlikView AccessPoint reports?
The first user opening it will increase the memory by the same amount as the .qvw will use when opened on the QV Desktop. As a rule of thumb, you can say that every additional user may use 10 - 15 % of the memory the first one used. When all the users leave, the server may wait some time before removing it from the memory. Unless you use pre-load option, then, the .qvw will be on the memory according to the pre-load schedule.
Second, is qvs.exe related to Windows Services "QlikView Server" services?
Server memory usage is 90% full, would restating QlikView Server services free up the memory?
I guess that if you are not using a version with problems, you would just force the elimination of .qvw from the memory.
Third, where is the best place to restart the services? I don't see it in Enterprise Management Console. Do do I restart in Windows Services?
I think it's just at the server Windows services control (services.msc). You could create a .bat for that you call it from prompt:
net stop "service name"
net start "service name"
Would restarting have any risk on the existing reports? Just a simple restart should have miminum inpact to End User?
I wouldn't restart it when the server is writing a file back after reload... but maybe it would just wait for the end before stoping.
I'm not sure about the other questions.
Hope this can help for now...
Answers to the rest of the questions.
1. DSC is the Directory Service Connector, and not the same as QDS, the Qlikview Distribution Service.
2. When a qvw is reloaded on a qlikview server, with or without Publisher license, the actual reload will always be done by the qvb.exe process. Qvb.exe is more or less a qv.exe, but with no user interface, and stands for QlikView Batch. Qv.exe is the Developer/Desktop process. When reloading in developer desktop, qv.exe will do the reload itself.
A quick followup question.
I'm using QV 10 SR1.
To sum it up, QV uses lots of memory (when users are logged on or when charts are opened by the users as they are cached on the server).
If two users look at the same chart with the same filter, does it store x amount of memory or 2x (two users)?
Here's my server setup - duo core 7.5 GB RAM
Currently servicing 20 users with 20+ reports (20 charts). What would be the typical memory size you want on the QV Server?
Do you have a best practice for monitoring the usage of your QlikView server resources. You mentioned QV usually consumes 90% of RAM and that's business as usual. How do you proactively monitor when you QV server is approaching it's limits and needs more RAM before your users start suffering?