I have using a dedicated server, website is also fully optimized.but whenever I share blog links on Facebook, site load time increse drastically. When traffic comes, site load time goes hoto 50 sec. Couldn't find the solution. Please help. Here is the websites
Related
when I visit my website the first time the access is really slow (not the downloading of the page, only waiting before the access), but after the first time I visit the website the navigation is normal and fast.
Someone can kindly help me making some tests?
Thanks
Alex
Firstly whenever you visit a site for the first time, your local server will resolve the DNS resolution, more precise will translate the page name into an IP address. The upcoming times the IP address is cached(Store onto your PC or your local server).
Secondly has something to do with saving some of the web page data into your device, basically the second the web page content may be already stored into your device, but that depends on the actual website which you are browsing on.
My Jekyll website is currently powered by a shared web hosting plan from HostGator with unlimited disk space & bandwidth. I have also enabled CloudFlare for the site.
I've heard about Heroku which hosts websites for free and GitHub Pages. I won't exceed 2TB bandwidth/month nor do I need more than 300 MB space so I comply with both GitHub Pages & Heroku's limitations.
Which of the following will serve the website fastest to users (and with the max uptime)?
Shared web hosting (I deploy via rsync)
GitHub Pages
Heroku
I think shared web hosting is slower than Heroku or GitHub Pages. So, what should I use? Is GitHub Pages faster than Heroku with 1x dyno?
My website gets about 15k pageviews/daily.
GitHub Pages uses Fastly, a CDN, to deliver its content. Unless you're using a similarly fast and efficient caching system, you'll see that GitHub Pages is fastest.
Jeremy Morgan wrote a great piece some time ago wherein he compared GitHub Pages to several other services. He found that GHP is the fastest of the four services he tested and recommends GHP. He doesn't have any data on Heroku, but setting up your site to work with Heroku shouldn't take that long. You can compare speed with webpagetest.org, as Jeremy suggests.
If your 15K pageviews see a lot of overlap (i.e. mostly the same collection of pages/assets being loaded), then you'll find that Fastly on GHP offers you better page load times than other services.
I hope someone can help me figure out this issue.
I have a windows based VPS with 6GB of ram and enough disk space.
I have only 3 websites hosted and all three are not advertised publicly, so no one could access.
The issue is the server is slow in response whenever we try to load the sites in browser or in RDP or thru Parallel Plesk Control. Everything slow to response.
I have every 1 minute to 3 , from green zone to red zone a lot of numsessions limit hits.
I have browsed SO and read Parallel doc and even browse their forum and no one has mentioned a real solution. They say that numsessions is hit when many sessions of rdp or Parallel Plesk Control are left open.In my case no one has access to the server and no one is logging to the server either. I have rebooted the server many times and only one session was open and that was to control server via virtuoso (Parallel Power Control) and same the numsessions is hit again within 3 min of reboot.
I have talk to the idiots at 1and1 (where we bought the VPS xxl) and they have no clue saying it is not our problem but yours or MS Windows! I have not installed any third party or even proprietary software on server which could cause the issue. The server is brand new and only created new sites via Parallel Plesk control. Emails are not working either.
Windows Event viewer doesnt show much information either.
Last resort is to re-image the server which may solve issue but I doubt since the issue seems to be from the server when we bought it.
anyone could shed their wisdom light on this please?
Thanks
Just noticed my resource log full of these as well. I think the issue is that a session is counted as soon as a RDP connection is made - so bots trying common admin passwords count towards this.
The real issue is as there is no way I can find to filter these from the resource alerts you basically can't find the real problem you have as the logs are just full of numsesssions.
Sometimes when I access my windows azure website, the initial response time is very slow. After the first page load the website is fast. Some background: The website is not that often visited at the moment. Further, I am using a keepalivecontroller to keep the website running and the website is running in shared mode. I am wondering: are websites that are not that active removed from memory in windows azure? Or is it just that background tasks on the operational level of windows azure are interfering sometimes? It is not transparent for me what is happening, so is there some sla of something for windows azure websites?
There is now a new feature available for Windows Azure Websites in 'Reserved' mode that will keep your website warm. You can now turn on "Always-on" under the "Configuration"-tab on your Azure Website. As explained in this blog post:
When the new “Always On” feature is is enabled on a site, “Windows
Azure will automatically ping your website regularly to ensure that
the website is always active and in a warm/running state,” Guthrie
writes. “This is useful to ensure that a site is always responsive
(and that the app domain or worker process has not paged out due to
lack of external HTTP requests).”
Easiest way to keep a website warm is to call it regularly using the Scheduler feature in Windows Azure Mobile Services.
You simply write a script in the Scheduler that pings your website every x minutes.
Here's a post covering how to do that: http://fabriccontroller.net/blog/posts/job-scheduling-in-windows-azure/
The Windows Azure Web Sites are still in preview, so there is currently no SLA with that service.
The Web Sites do idle out when in free or in Shared mode, which is likely what you are seeing. When the site idles out it actually is removed from memory, and indeed the IIS process host running the site is shut down. This is how they can get the density of hosting 100 sites on the same VM.
You can find a lot of info on the Channel9 site about why this is the case, or, as a shameless plug, here is an article that talks about how the process is handled.
Now, you mentioned that you were using a keepalivecontroller, but what exactly do you mean by that? I use pingdom.com to contantly request data for one of my websites, and that seems to do pretty well. It is still possible that a request doesn't come in and the idle time is met which then cycles the site. It is also possible that even if you always have the site running that the VM the site sites on needs to have the underlying OS updated, in which case Azure would then move the site process to another VM, which could also cause the slow start up on the next request.
I'd start logging your application start ups and then look through your logs to see how often that is happening.
If you only need to warm it up once (vs keeping it warm) and are mostly trying to prevent your customers experience page cold starts, I believe the correct tool is IIS Application Initialization. You can configure it with a list of urls to hit before it deems the app ready for action.
My site is suffering from page cold starts and that is severely magnified in Azure Websites (even on an S3), but it is absolutely speedy after its served that first time thanks to several layers of caching (our inefficient use of Umbraco's dynamic nodes query language creates a lot of database churn--which we're cleaning up opportunistically).
From what I've read and my own web.config attempts this is still not available in Azure Websites. I've asked Microsoft for it here: MS IDEA: Application Initialization to warm up specific pages when app pool starts. Please consider voting for it.
For each service/site you need to go to "Configure", then switch "Always On" to ON. Also make sure you click Save; it took my website about 2 minutes before noticing the change.
Why this is not the default is kind of mind boggling, because my setup on HostGator was running much faster than Azure. I guess Microsoft is figuring if nobody is accessing your site, it's okay if it has a long load time.
We have a fairly large member site set up on AWS using a medium high-CPU server. Most of the time it runs at very low capacity (~3%), but once a week we send out a newsletter to our members with opportunities. In the minutes after the newsletter the server load shoots up (sometimes to over 100%) with members trying to access the site.
In the long term, we will be restructuring the system, but for now, I'd like to add an overflow server that will serve a 'try back in a few minutes' page to users while this is occurring.
I haven't been able to find any good how-tos on setting up routing for this type of thing. Any ideas?
Thanks!
Why not use Elastic Load Balancing along with Auto Scaling instead?
That would allow you to match the number of servers to your actual usage. Most of the week, you would not be paying for 97% unused capacity, and during the newsletter periods, you will have enough capacity for everyone to log on and buy something from you.
There is a post on the Amazon Web Services blog that explains how to do this. It puts failover web page on S3, which is easy to maintain and cheap.
Create a Backup Website Using Route 53 DNS Failover and S3 Website Hosting