- Newest
- Most votes
- Most comments
I'm writing to
D:\PhotonUser\AppName\Cache\
Some observations:
Sometimes a new user will get the "Not Enough Drive Space" warning; when the AppStream session is closed and then reopened, they can perform the exact same operation and it succeeds.
For cases where reopening the session doesn't work, I've found that if I expand the virtual hard drive in S3, the issue may be resolved for that user (though other users may experience the behavior in the above bullet).
https://docs.aws.amazon.com/appstream2/latest/developerguide/administer-app-settings-vhds.html#app-persistence-increase-VHD-size indicates how to increase the virtual hard drive, but it is per user.
Can I change the default VHD size for new users in an AppStream application?
Thanks!
Hi Prism -
Can I change the default VHD size for new users in an AppStream application?
We don't support this today. I will take it as feedback for a future enhancement of the feature. Because AppStream needs to download the full VHD from S3 prior to starting the streaming session, increasing the size of the disk will increase the amount of time it takes for a users streaming session to start, if they're filling it.
Depending on the type of data, I would suggest instead writing it to the Home Folder feature, as it is hydrated on access versus at session start.
That said, 100mb in general shouldn't cause too much of an issue. I would suggest seeing what applications are consuming the 1gb to see if they can be changed. For example, if an app is writing temporary data to the VHD that isn't needing to be persisted, you can move that to the C: drive directly.
Hope that helps.
Murali
Thank you Murali, that's very helpful. I will look into writing to the C drive instead.
Are there space concerns for doing this? If we have multiple streams for multiple users are they using the same C drive (which could cause conflicts)?
Are there privilege concerns for doing this? Can any user write to C:\ProgramData, for instance?
Thanks again.
We provide every user with a dedicated streaming instance. Hence only the user who is using the streaming session has access to the C drive of the instance supporting that session.
I have changed to using C:\ProgramData and have not seen drive space warnings. Hopefully that will work going forward.
Thank you very much for your help!
Relevant content
- asked 6 years ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago