I'm currently running Windows 10 with the new containers, and am looking for help on container cpu and memory usage, both for a relatively lightweight workload and if someone has installed the SQL Server 2014 or 2016 images, what their memory footprint is? I'm just trying to get a better handle on memory requirements, so I can do a better job of planning server sizing. I'm just interested in the memory working set as reported by Task Manager in Details view.
Related
I want to make performance graph like I did on Windows Remote Desktop using performance monitor.
Is it possible to get performance data (i.e. avairable memory , CPU usage) with only CUI (I'm using TeraTerm)?
I want to run some performance tests against a Quarkus native image. In a traditional Java application I would use VisualVM to connect to the application and monitor its memory (young gen, old gen, etc.), CPU usage, threads and so on.
Since native images are now OS processes, is there a way to get insight information of the proccess equivalent to what we got with VisualVM or should we just stick to the OS information (CPU usage + memory)
One option if you add the metrics extension is to fetch them and after plot in some way. Other option could be vmstat on unix, but you have them for the whole system.
If you deploy in a kubernetes environment prometheus fetch the information for you.
question, how much resources I need to run apache usergrid?
I mean hardware resources, RAM CPU
I want to deploy apache usergrid to be used as backed in our apps, the apps have a low traffic now, are custom projects to be used in small users groups (<10k)
I want to know the minimum requirements to know if it is viable for us, thanks.
From what I see of usergrid, I can think that the most hungry for resources component will be Elasticsearch, so to have a production environment that's working well, I guess you should start following ES' requirements:
At least 8 GB of RAM
At least 4 cores (the more cores you give Elasticsearch, the more love you get as it tends to works with a lot of threading, i.e. give more cores rather than more CPU processing power)
Fast HDDs should perform fine
See this article on Elasticsearch.A last thing is that depending on your system, you can tune several settings on Elasticsearch to achieve a better throughput. (For instance see https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-indexing-speed.html)
I have deployed latest version of Usergrid i.e. 2.1, which is working smoothly in apache-cassandra-2.1.20, apache-tomcat-7.0.85, elasticsearch-1.7.6 on single node of Cassandra on Ubuntu 16.04 with 8 GB Ram and 180 GB SSD. Hope this will help you.
I use this version on my dev environment : Redis-64 .
And I want to know if this version is suitable for the production environment?
If can use, then compared with under Linux, what need to be pay attention to?
Since version 3.0.3 the windows port developers abandoned the dlmalloc and began to use jemalloc as memory allocator. And the port was actually considered for production usage. The 3.0.500 build is approved for production by ms developers (see here).
And there is some kind of hell so how they bypassed the unix fork to save data to disk. Microsoft developers port call it point-in-time heap snapshot. And this is the most controversial part when used in production:
Redis under windows may need up to 3 times more memory than you need in linux version. This behavior is considered normal, because swap file in the windows can easily be up to 3 times larger than the actual amount of RAM.
I think this is acceptable only if the use Redis as LRU cache or not to save data to disk at all.
At least Redis under windows is absolutely susceptible if you Redis node use lot of memory. For example - we try to use Redis for windows (v2.8, v3.0.3, v3.0.5) on server with 512 gb of memory with 2 SSD drives (each 256 gb in raid 0) used as system disk. No any limits on windows swap file. Our test emulates our production - lots of writes and saves with RDB with utilization ~60-70% of memory. And here is was lots of hands up behaviours then this node try to save snapshots - memory consumption jumps, connection freeze during saving. Such behaviour never happens undex linux on same hardware.
If you are handling all your own licensing(working under a BizSpark license), is it possible run Windows on an EC2 instance marked for Linux/Unix?
I am considering migrating a dedicated server I have to EC2 but was not able to find guidance on this. I have been told that you get complete control over the instance to install whatever you like, but wanted to know if anyone else has tried this. Thanks for the info!
Update:
Replacing a dedicated virtual with 512MB memory and 10GB storage. Hosting mostly one-off sites and blog or three.
I remember that this was possible before Amazon supported Windows instances natively. You may want to check the links below to follow the discussions on the topic from the 2006-2008 era.
However you have to take into consideration that you will lose performance and you will complicate your setup significantly. The small Windows instance costs only about $18-$22 more per month compared to a small Linux instance, so I believe you have to evaluate if this gain will be of more value than the performance loss and setup complexity.
Related Links:
How To Forge: Running Windows on the Amazon Elastic Compute Cloud with Qemu and Linux
AWS Forums: QEMU / Windows Server 2003 / Fedora Core 6 Public AMI
AWS Resources: Windows Server 2003 on Fedora Core 6 [Qemu] V.1.1
It was possible before to bring your own License of Windows to Amazon under the Windows License Mobility Pilot but it seems to have been killed off... the API still exists though, so maybe its something they will bring later... I dont know the details, but i think you got the instance at the same price as you would a Linux instance, and no loss in performance either...