Generaly i would say No, dedicated 2G machine can't handle 100k unique traffic per day and the server will have lots of paging and delays from from your machine but then again, how small a foot print one user access your web server will determine how many can access your server simultaneusly.
From the Godaddy website the economy 2GB package appears to have the following specs
OS: Linux CentOS, CPU: Intel® Pentium 4 - 3.0 GHz, RAM: 2 GB
You can use your current 2GB setup and know if maxclient settings can still be increased. the sample on the below link is based on a 512 system and 1 user access only. just do the same procedure for your 2GB system and know how much maxclient can still be allocated..
Note: factors to determine how much connections can a web server handle will be based on acceptable memory paging, httpd process virtual memory size and free memory
simultaneus traffic will be the concern here, how much can the free ram accomodate and if maxclient settings are correct (how much httpd simultaneus processes can be active at a given time) before too much memory paging sets in.
To calculate how much performance you can get from 2GB ram in Centos web server please see below link:
http://beginlinux.com/blog/2008/11/performance-tuning-a-centos-web-server/
-clip-
Formula for Determining MaxClients Setting
Check the average Apache process by opening up top and then divide this size into the available memory. Of course it is important to leave a little extra. Here is an example of the process. Note that top shows one of the PIDs as 1383 for apache. This process is using 12,200 KB of virtual memory. So to follow the formula you would take the total available memory and divide by 12,200 KB or about 12 MB. That would provide you with the number of MaxClients you could add. However, you will see in this example that this server is using almost all memory so it would be unwise to add any to the MaxClients number.
top – 15:47:15 up 21 days, 33 min, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 34 total, 1 running, 32 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 100.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 510992k total, 498468k used, 12524k free, 63152k buffers
Swap: 1145572k total, 592k used, 1144980k free, 258728k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1 root 16 0 2304 608 524 S 0.0 0.1 0:00.02 init
5549 root 16 0 2192 548 460 S 0.0 0.1 0:00.37 syslogd
5583 root 16 0 4680 1140 836 S 0.0 0.2 0:11.00 sshd
5597 root 22 0 2260 792 660 S 0.0 0.2 0:00.00 xinetd
5614 clamav 16 0 49988 34m 1004 S 0.0 7.0 0:33.98 clamd
5668 root 16 0 5824 1600 1268 S 0.0 0.3 0:01.59 master
5697 root 16 0 3856 916 524 S 0.0 0.2 0:00.01 crond
14265 named 21 0 49748 4512 1916 S 0.0 0.9 0:21.54 named
26346 root 19 0 5332 812 572 S 0.0 0.2 0:00.00 saslauthd
26347 root 18 0 5332 480 240 S 0.0 0.1 0:00.00 saslauthd
26348 root 19 0 5332 436 196 S 0.0 0.1 0:00.00 saslauthd
26350 root 19 0 5332 436 196 S 0.0 0.1 0:00.00 saslauthd
26351 root 19 0 5332 436 196 S 0.0 0.1 0:00.00 saslauthd
1362 root 16 0 5020 868 648 S 0.0 0.2 0:00.23 dovecot
1365 root 16 0 5740 1524 1048 S 0.0 0.3 0:04.80 dovecot-auth
1383 root 16 0 12200 5160 3524 S 0.0 1.0 0:00.28 httpd
5537 postfix 16 0 7172 1656 1320 S 0.0 0.3 0:02.44 qmgr
service httpd status
httpd (pid 1907 1906 1905 1904 1903 1902 1901 1900 1383) is running…