For testing purposes Tableau says 4 cores, 8 GB RAM and 15 GB disk space.
But recommended one says 8 physical cores, 32 GB RAM and 50 GB disk space.
Now I am stuck as 2nd configuration seems to be an overkill. I don't have heavy requirements. How should I decide on cores and RAM?
I shall be connecting Tableau to MySQL for real time dashboards
"Tableau Server will not install if your computer does not meet the
minimum requirements"
See the absolute minimum requirements here: http://onlinehelp.tableau.com/current/server/en-us/help.htm#server_hardware_min.htm
The minimum configuration recommended for production usage of Tableau Server is based on these hardware specifications:
Single computer
64-bit processor
8 physical cores, 2.0 GHz or higher CPU
32 GB system memory
50 GB minimum free disk space
Read more here: http://onlinehelp.tableau.com/current/server/en-us/help.htm#requ.htm
Also, if you don't want to supply your own physical hardware you can always install on a VM. Check out the Tableau Server Bring-Your-Own-License program on AWS
Related
So I recently have a project using MySQL 8.0.12, configured for Development Computer upon installation.
I developed the system on my PC, which has an i5 CPU with 8 GB RAM.
On my PC, the mysqld.exe process consumes around 10% of CPU usage and 20 MB of Memory when a continuous query is run
I then deployed this system to the client PC, which has an Atom CPU with 8 GB RAM. Also using a fresh install of MySQL 8.0.12.
For some reason, even on idle condition, the mysqld.exe process consumes 300 MB of Memory. Also the CPU usage goes up to 60% during continuous query.
Both system runs on Windows 10 x64-bit
Obviously the speed of these two computers are different, but I kind of doubt that the CPU core is the issue, since the idle state already consume different memory.
What may went wrong with this MySQL inside the Atom based PC? Why does it behave very differently? CPU Usage aside, it is very weird to me that the idle state memory consumption is so different.
Is there any possible workaround to these issues?
On my CUDA program I see large variability between different runs (upto 50%) in communication time which include host to device and device to host data transfer times over PCI Express for pinned memory. How can I explain this variability? Does it happen when the PCI controller and memory controller is busy performing other PCIe transfers? Any insight/reference is greatly appreciated. The GPU is Tesla K20c, the host is AMD Opteron 6168 with 12 cores running the Linux operating system. The PCI Express version is 2.0.
The system you are doing this on is a NUMA system, which means that each of the two discrete CPUs (the Opteron 6168 has two 6 core CPUs in a single package) in your host has its own memory controller and there maybe a different number of HyperTransport hops between each CPUs memory and the PCI-e controller hosting your CUDA device.
This means that, depending on CPU affinity, the thread which runs your bandwidth tests may have different latency to both host memory and the GPU. This would explain the differences in timings which you are seeing
On my CUDA program I see large variability between different runs (upto 50%) in communication time which include host to device and device to host data transfer times over PCI Express for pinned memory. How can I explain this variability? Does it happen when the PCI controller and memory controller is busy performing other PCIe transfers? Any insight/reference is greatly appreciated. The GPU is Tesla K20c, the host is AMD Opteron 6168 with 12 cores running the Linux operating system. The PCI Express version is 2.0.
The system you are doing this on is a NUMA system, which means that each of the two discrete CPUs (the Opteron 6168 has two 6 core CPUs in a single package) in your host has its own memory controller and there maybe a different number of HyperTransport hops between each CPUs memory and the PCI-e controller hosting your CUDA device.
This means that, depending on CPU affinity, the thread which runs your bandwidth tests may have different latency to both host memory and the GPU. This would explain the differences in timings which you are seeing
I am developing a WP8 app on a memory-constrained machine.
I can only run my app on the smaller-resolution emulator, but not the rest, because those require 1 GB of system ram.
How can I change the configuration for the emulators so that they use less memory?
I'm afraid there is no alternative but to add more RAM to your system (RAM is cheap these days).
For your information, here are the requirements for the Windows Phone 8 SDK:
6.5 GB of free hard disk space
4 GB RAM
64-bit (x64) CPU
Try the following solution
https://docs.google.com/document/d/1sTelfYz-oiQ98GSqPn-IBU7J0XTY24HocEU_mhxZFP0/edit?usp=sharing to edit static emulator RAM settings.
Does it make a difference? All I'll be doing (for the most part) is running different browsers. I would think the most stripped down one possible would be best.
Update: My dev box is a MacBook Pro (2010) with 8G ram, 2.4 GHz processor running Lion.
Ordinary Windows 7 installations are shipped with a full load of crap. Even the cleanest installs have a size of at least 10 GB. For that reason, I recommend to only use Windows 7 if you want to test IE9+ (which requires Vista+).
The following steps will take a maximum of ten minutes. Afterwards, you have a fully functioning Windows 7 + IE9 system, which takes only 2GB of physical space:
Getting Windows 7 Lite
I use this set-up in VirtualBox. I have not tested it in VMWare, but there should be no differences.
Get a Windows 7 Lite VM image.
I myself use an image, created by ivankehayov:
Download name: Win7.SP1.IE9.lite.v2-IK
ISO size: 700 MB (after installing: less 2GB)
MD5: 094BE542B3F292726EF7F16619CACA9A
For more information, and the tools used to create this image, see this forum. More details (about the old image) can be found here.
Creating/Installing the Virtual Machine
Create an new VM, and put the ISO image in the virtual CD slot.
2 GB RAM (Minimum of 1 GB, to ensure that your system doesn't crash).
Boot the Virtual Machine.
Install from the iso image
Decrease resource usage (4 steps)
Install CCleaner, to wipe (temporary) (log) files.
Disable System Protection:
Control Panel > System Protection > Configure... > Turn off system protection
Disable the page file (especially recommended when you've got a SSD).
Control Panel > Advanced system settings > Performance [Settings..] > Advanced > Virtual memory [Change..] > No paging file - Set. Confirm and reboot.
Disable all unnecessary services, to increase the booting speed.
Set your preferences (homepage? IE settings?), and save a snapshot of your VM. When you're done with using the VM, restore the snapshot. This will prevent Windows from hogging disk space over time, and keeps your VM image compact.
My virtual Windows 7 boots within 45 seconds.
Relevant details about my own environment:
- Virtualization software: Oracle VirtualBox
- Operating system: Linux-based
- RAM: 8 GB
- Disk: 60 GB SSD