Andrew G. Allen - Latest Comments

Re: http://www.andrewallen.co.uk/blog/citrix-web-interface-and-the-fatal-execution-engine-error/

Fernando — Wed, 06 Feb 2013 06:33:18 -0000

http://support.citrix.com/a...

Re: http://www.andrewallen.co.uk/blog/cname-is-out-hello-aname/

Richard — Thu, 28 Jun 2012 14:32:52 -0000

Each page view is not a query (unless your set your TTL to one second). Generally your worst case is that each "session" (or a time a user visits your site) is a query. But this is overly aggressive as well.

It is actually almost impossible to predict how many queries you will receive without knowing not only what IPs your customers are coming from but also the network configuration for each one of your customers. Since this is not possible you can rough (and worst case) number by this calculation.

(Take the average seconds the average user stays on your website) / (TTL of your record)
Multiply this by the total number of sessions per day
Multiply this by the number days in the month
Add one for each email received. Add one for each email sent.

Example:
The average user stays on your site for 10 minutes.
Your record TTL is 5 minutes.
So the average user will cause you 2 queries per visit. (10 / 5 = 2)
You have 10,000 visits per day (2 * 10,000 = 20,000 queries per day)
You have 31 days in the month (20,000 * 31 = 620,000 queries per month)
So you would have 620,000 queries in the month from web traffic.
Take number and add it to the total number of emails received.
So if you received 5,000 emails and you sent 5,000 emails, then your total queries would be 630,000.

This is of course a rough estimate and it is usually a worst case number. Since many users would share the same resolving name server then they actually share the same query.

The ANAME records would not impact your monthly query count anymore than a CNAME would. In fact if you are creating a ANAME to another domain within DNS Made Easy it would actually save queries since there is no longer the requirement to do a double lookup.
There will be a minimal amount of checks against your domain if your target to your ANAME record is within DNS Made Easy, but nothing that should exceed a few thousand queries per month. This will generally save users on queries as well though since it would involve a double-lookup normally.

Re: http://www.andrewallen.co.uk/blog/cname-is-out-hello-aname/

Andrew G. Allen — Thu, 28 Jun 2012 06:38:16 -0000

I guess it would depend on a lot of factors - the TTL on the individual records would influence the length of time various downstream DNS and proxy servers would cache look ups done from clients on those networks, but also once a client has initially accessed your site for a browsing session, it won't need to do any other look ups for that session, while potentially browsing an unlimited number of pages on your site.

The other aspect is records not used for the website itself, such as MX and NS records - I am using vanity DNS which will increase the number of monthly queries on its own, but if you also receive a high volume of email, that will also increase the query count.

For records which I know won't change very often (such as the MX records pointing to Google Apps), I set a high TTL to reduce the impact to the query count, but I am no where near the limit on my account to really worry about it too much - and my sites are not receiving slashdot like traffic :)

So although your account is 5 million queries, it won't equate to 5 million PVs.

One question I have for DNS Made Easy, is that does the nature of how the ANAME records work, impact the monthly query count against my account, as I have no control over how often the referenced hostname is checked? I can only control the TTL on my records, i.e. the resulting A records that are returned to look ups against my zone.

Re: http://www.andrewallen.co.uk/blog/cname-is-out-hello-aname/

ksec — Thu, 28 Jun 2012 05:35:55 -0000

Just wondering how does the 5 Million Queries per Month works out for you? I could never figure out the maths behind it, Since every pageview would require more then 1 query, theoretically i am limited to 5 Million PV per month?

Re: Citrix Web Interface and the Fatal Execution Engine Error [updated]

Andy — Mon, 19 Jan 2009 12:37:13 -0000

http://forums.citrix.com/me...

The bottom post fixed the errors.

Re: Acronis True Image Echo Server on CentOS

arbert — Sun, 12 Oct 2008 13:33:59 -0000

I'm glad I found your blog. I downloaded the i686 file and it was like "duh, what now". Also a Windows guy and I had NO CLUE. I'm a bit surprised at Acronis, they're usually pretty good at Install and Documentation

Re: Citrix Web Interface and the Fatal Execution Engine Error [updated]

Gary — Thu, 01 May 2008 17:00:51 -0000

I came across a very similar error as you. My setup was win 2003 R2 standard SP2 64bit running in a VMWare Server version 1.05. The .net framework was just not stable and any applications using it often crashed. I had SQL Server 2005 running with Reporting Services and the reporting services service would often fail and many of the sql client tools would also crash.

After spending over a week on the issue I upgraded to VMWare Server 2.0 (beta) and all of my problems went away. The docs for the new version state that they made changes to the way memory was being handled specifically towards 64bit OSes.

Maybe a newer version of citrix (if one even exists) would help you?