The Core Technologies Blog

Professional Software for Windows Services / 24×7 Operation

Windows Services Startup Types Explained

Windows Services Startup Types Explained

What is a service’s Startup Type? Where do I find it?

A Windows Service is a special application whose lifecycle is managed by the operating system. That is, unlike a “normal” application that relies on a person to start or stop it, Windows itself is responsible for starting, stopping or restarting a service.

To give you some control over how things work, each Windows Service has a startup type property that dictates how Windows should manage it. The options range from “start it as soon as you can” to “don’t run the service at all”. There’s even the ability to start a service when certain conditions are met. But more on those later as we dig into each of the startup types below.

The built-in Services application shows the startup type for each service. You can launch the application by typing “services” into the search bar and clicking its icon:

Start Services from the search bar

The Services window lists all the Windows Services running on your computer. The “Startup Type” column indicates how each service is configured to start:

Services: The Startup Type column

Double-click a row to reveal the details of that service in the Properties window. You’ll see the “Startup type” field about half-way down:

Service properties: The startup type field

If permissions allow, you can change the startup type right there as well. Simply choose a new value from the list and click OK (or Apply) to record your change:

Changing the Startup Type

And now that you know how to find the startup type of any service, let’s review the values available and what each of them means.


When a service is set to “Automatic”, Windows will start it as soon as possible whenever the system boots.

Because of that early start, all critical Windows Services — like those supporting networking, security and user management — are set to start automatically. That enables them to come to life quickly, to support key functionality across your computer.

When to set startup type to “Automatic”

Automatic start is best for services that:

  • Implement technical functions that are vital for the operation of your PC;

  • Are needed to support other services or applications;

  • Must run all the time.

Examples of “Automatic” services

Many of the built-in Windows Services are set to start automatically. Here are a few examples:

  • Windows Defender Firewall — helps protect your computer by preventing unauthorized users from gaining access to your computer through the Internet or a network. This service must be ready by the time the network is up.

  • Local Session Manager — a core Windows Service that manages local user sessions. Stopping or disabling this service will result in system instability.

  • Windows Event Log — manages events and event logs for other services. Stopping this service may compromise the security and reliability of the system.

Automatic (Delayed Start)

Windows launches “Automatic (Delayed Start)” services about 1-2 minutes after your computer boots — after Automatic services have started.

You can think of Windows launching services in two rounds at boot. Automatic services go in the first round while “Automatic (Delayed Start)” services are kicked off in the second round.

As such, the “Automatic (Delayed Start)” setting is most useful in lessening the mad rush for resources when your computer starts up.

For example, suppose that there are 20 services all being started at the same time. In reality, they will all be competing for slices of the machine’s precious resources (CPU/RAM/Disk/Network). The inevitable result is that each service will take longer to become available.

If you have a few services that are critical, then you may want to set those few to “Automatic” and set as many of the others as you can to “Automatic (Delayed Start)”. This will ensure that the critical services get the most resources early and become available sooner, while the non-critical services start a bit later (which by definition is OK).

When to set startup type to “Automatic (Delayed Start)”

“Automatic (Delayed Start)” is best for services that:

  • Should start at boot but don’t perform mission-critical activities;

  • Are best started after supporting services are up and running;

  • Should run all the time.

Examples of “Automatic (Delayed Start)” services

On Windows 11, less than a dozen of the built-in Windows Services are set to start delayed. Here are a few examples:

  • Security Center — monitors and reports security health settings on the computer. This service should run all the time but there is no need to start it ASAP because it’s focused on reporting.

  • Update Orchestrator Service — manages Windows Updates. If stopped, your computer will not be able to download and install the latest updates. Since it’s not a critical service, Windows starts it in the second round.

  • Dropbox Update Service — keeps your Dropbox installations up to date. The service is certainly helpful but it doesn’t need to start the instant your PC reboots.


A “Manual” service isn’t automatically started by Windows at boot. Instead, it will be started on demand — either by a user or by an application.

For the most part, “Manual” services sit idle until they’re needed. And often, they return to an idle state once they’ve performed the work they were summoned to do. As such, they tend to be the most efficient group of services, only running when they need to.

Note that in previous versions of Windows, the vast majority of services were set to “Automatic” and only a handful were “Manual”. But over the years, as Microsoft focused on streamlining the boot process, the situation has fully reversed. Most of the built-in Windows Services are now started on demand!

When to set startup type to “Manual”

The “Manual” startup type is appropriate for services that:

  • Don’t need to run 24/7;

  • Are only used occasionally;

  • Provide uncommon functionality that only some devices (or users) will need;

  • Aim to achieve maximum efficiency, only running when necessary;

Examples of “Manual” services

Many of the built-in Windows Services are set to “Manual”. Here are a few examples:

  • Windows Backup — provides backup and restore capabilities, which are only necessary at defined times.

  • Fax Service — enables you to send and receive faxes. Who uses that anymore? 🙂

  • Microsoft Edge Elevation Service — keeps Microsoft Edge up to date. This service only comes to life a few times per day.


Setting the startup type to “Disabled” tells Windows don’t allow the service to start — under any circumstances. You cannot run a disabled service.

If you wish to start a disabled service, you must first change its startup type to another value. Setting to “Manual” usually makes the most sense.

When to set startup type to “Disabled”

You should disable services that:

  • Shouldn’t (or cannot) run;

  • Are responsible for unused functionality;

  • Are insecure and may compromise the system in some fashion.

Examples of “Disabled” services

Here are a few examples of services with startup type set to “Disabled”:

  • Shared PC Account Manager — Manages profiles and accounts on a SharedPC configured device. It’s disabled on our machine because we’re not using the SharedPC feature.

  • OpenSSH Authentication Agent — holds private keys used for public key authentication. Citing security concerns, Microsoft disables this rarely used service in new installations of Windows 10 & 11.

  • Remote Registry — enables remote users to modify registry settings on this computer. Certainly not for everyone!

Intermission: What does “Trigger Start” mean?

Because the remaining startup types all mention “Trigger Start”, we thought this would be a good time to explain what that means. Here goes…

In older versions of Windows, the only startup types available were the ones we’ve already reviewed — Automatic, Automatic (Delayed Start), Manual and Disabled. Each service was assigned one of those values. (Incidentally, most were set to “Automatic”, which made for utter chaos as they all scrambled to start at boot.)

However, in Windows 7 (circa 2009), Microsoft introduced a new capability — the ability to start (or stop) a service when a key operating system event occurs. They called those events triggers and services that react to the events trigger start services.

Putting it all together, a service has “Trigger Start” in its startup type if it has at least one trigger.

But why did Microsoft introduce trigger start services?

Well, by offering trigger start as an option, Microsoft made it easier for Windows Services to avoid starting at boot and running 24/7. For example, if your service works with USB drives, you can configure it to start whenever someone inserts a USB drive. Similarly, a network-monitoring service may choose to run only when your computer signs out of a domain or leaves the network. Options abound, and you can read about the technical details in the Developing Efficient Background Processes for Windows white paper.

So service triggers are great. But there is one major inconvenience…

You can’t view or edit triggers with the Services application

Until Microsoft updates the Services application to manage triggers, you either have to:

  1. rely on the Windows SC command-line program, or

  2. use our free Service Trigger Editor GUI utility, which shows you all the trigger start services on your system:

Service Trigger Editor managing trigger start services

Anyway, back to startup types…

Automatic (Trigger Start)

“Automatic (Trigger Start)” means start the service immediately at boot — and also restart it whenever specific operating system events (triggers) occur.

It’s the same as Automatic, plus with one or more triggers too.

As a result, an “Automatic (Trigger Start)” service can be very efficient. Even though Windows starts it as soon as possible, the service can do its initial work and quickly exit — secure in the knowledge that Windows will fire it up again whenever it’s needed.

When to set startup type to “Automatic (Trigger Start)”

“Automatic (Trigger Start)” start works best for services that:

  • Should to start as soon as possible after boot;

  • Don’t need to run all the time;

  • Can be reactivated by a triggering event.

Examples of “Automatic (Trigger Start)” services

On our Windows 11 computer, only six services are set to “Automatic (Trigger Start)”. Here are a few of them:

  • Server — supports file, print, and named-pipe sharing over the network. As you might expect, the two triggers are network-related:

    Triggers for the Server Windows Service
  • Windows Connection Manager — makes automatic connect/disconnect decisions based on the network connectivity options currently available to the PC and enables management of network connectivity based on Group Policy settings.

  • Group Policy Client — responsible for applying settings configured by administrators for the computer and users through the Group Policy component.

Automatic (Delayed Start, Trigger Start)

An “Automatic (Delayed Start, Trigger Start)” service starts a few minutes after boot — and also in response to a trigger.

As you may have guessed, “Automatic (Delayed Start, Trigger Start)” is similar to Automatic (Trigger Start), except that the service starts 1-2 minutes after boot (instead of ASAP).

When to set startup type to “Automatic (Delayed Start, Trigger Start)”

“Automatic (Delayed Start, Trigger Start)” can apply to services that:

  • Should to start at boot but can wait for a couple of minutes;

  • Don’t need to run all the time;

  • Can be reactivated by a triggering event.

Examples of “Automatic (Delayed Start, Trigger Start)” services

Few of the built-in Windows Services use this startup type. Here are three examples:

  • Microsoft Edge Update Service — keeps your Microsoft software up to date.

  • Software Protection — enables the download, installation and enforcement of digital licenses for Windows and Windows applications.

  • Windows Time — maintains date and time synchronization on all clients and servers in the network. Because it’s all about networking, the service will trigger-start when your computer joins a domain:

    The Windows Time domain service trigger

Manual (Trigger Start)

Windows never starts a “Manual (Trigger Start)” service at boot. It only starts the service in response to a trigger.

This is the most efficient startup type of them all. Windows only starts the service when its needed.

When to set startup type to Manual (Trigger Start)

“Manual (Trigger Start)” is a fine choice for services that:

  • Don’t need to start at boot;

  • Don’t need to run all the time;

  • Can be reactivated by a triggering event.

Examples of Manual (Trigger Start) services

“Manual (Trigger Start)” is the most popular startup type on our Windows 11 computer. That’s a testament to the work that Microsoft has put in to ensure that its services don’t hog resources by running when they don’t need to.

Example services include:

  • BitLocker Drive Encryption Service — provides secure startup for the operating system, as well as full volume encryption for OS, fixed or removable volumes. It only needs to run under special conditions (when a custom event is triggered).

  • Windows Update — enables the detection, download, and installation of updates for Windows and other programs. As you can see, the service will spring to life whenever a policy changes:

    Windows Update service policy triggers
  • Portable Device Enumerator Service — enforces group policy for removable mass-storage devices. It employs a dozen triggers!

    Portable Device Enumerator Service triggers

Windows Service startup types: Summary

To recap, the startup type tells Windows how it should start your service.

Here is what each value communicates to the operating system:

  • Automatic: “Start this service at boot, early in the cycle.”

  • Automatic (Delayed Start): “Start this service at boot, but delay it by a couple of minutes.”

  • Manual: “Don’t start this service at boot.”

  • Disabled: “Don’t start this service at boot, and don’t allow anyone (or any program) to start it either.”

  • Automatic (Trigger Start): “Start this service early in the boot cycle and start/stop it when specific events occur.”

  • Automatic (Delayed Start, Trigger Start): “Start this service a couple of minutes after boot and start/stop it when specific events occur.”

  • Manual (Trigger Start): “Don’t start this service at boot, only start/stop it when specific events occur.”

Posted in Windows Services | Tagged , , , , , , , , , , , | Leave a comment

OneDrive Doesn’t Sync Directory Junctions

OneDrive Doesn't Sync Linked Folders

What is a directory junction?

A directory junction is an alias of one folder to another.

Put another way, a directory junction allows you seamlessly access the contents of a folder from another directory, with a different path.

For example, let’s say that you have folder “C:\Users\Username\Documents\Media\All Movies” on your computer. However, you find that directory too long to type when working with it from the command line. You dream of entering a shorter path — such as “C:\Movies” — but you don’t want to copy the files to a new location.

To solve the problem, you would create a directory junction mapping “C:\Movies” to “C:\Users\Username\Documents\Media\All Movies”. After doing that, all your movies will be accessible from “C:\Movies” too. For all practical purposes, “C:\Movies” becomes a synonym for the longer path.

Directory junctions can be created with the with the mklink command. For example, this command creates the alias for the scenario above:

mklink /j "C:\Movies" "C:\Users\Username\Documents\Media\All Movies"

Why use a directory junction with OneDrive?

A directory junction provides convenience and flexibility when designing your cloud synchronization strategy. In theory, by allowing you to place any arbitrary folder inside your OneDrive folder, you can extend the scope of your OneDrive backup without having to duplicate large folders and files.

Let’s illustrate with a practical example.

Say you’ve installed OneDrive to synchronize your OneDrive folder (“C:\OneDrive”) with the cloud. Everything is working well.

However, you also want OneDrive to backup “C:\Shared\CustomerSuccess\Templates” — a shared folder with important company files. How do we instruct OneDrive to sync that folder as well?

Well, this is where folder linking comes in. You can create a directory junction in your OneDrive folder that points to the Templates folder, like this:

Create a directory junction with mklink

Doing so places an alias of the Templates folder right inside the OneDrive folder, as illustrated here:

The directory junction in the OneDrive folder

And soon after you’ve created the directory junction, OneDrive will notice the new linked folder and sync it to the cloud:

OneDrive has synced the linked folder

Problem solved, right? Unfortunately, not so fast…

OneDrive doesn’t detect changes to the files in directory junction

While OneDrive synced the contents of the new linked folder when the directory junction was first established, it didn’t re-sync the folder when something changed.

For example, when we created a new file called “evaluation-2023.docx” in the linked folder, OneDrive didn’t copy the file to the cloud:

OneDrive doesn't sync a new file in the linked folder

It’s as if OneDrive didn’t realize that the new file was there at all.

And the same was true for other changes too. OneDrive missed all deletes, renames and updates to the files in the linked folder. None made it to the cloud.

In fact, the only time OneDrive synced the linked folder was when the application started. Afterwards, OneDrive completely ignored the linked folder.

Needless to say, this unusual behavior renders the directory junction we created in the OneDrive folder useless. If we can’t rely on OneDrive to recognize changes to our files, why bother linking the folder at all?

But… why?

The reason is likely very technical — rooted in the low-level file system services provided by the Windows Operating System.

OneDrive probably calls FindFirstChangeNotification to monitor the OneDrive folder. And whenever a file is changed:

  1. FindFirstChangeNotification lets OneDrive know that something in the folder has been updated

  2. OneDrive figures out what’s changed and copies the new file up to the cloud.

However, FindFirstChangeNotification treats directory junctions and other links specially. From the Symbolic Link Effects on File Systems Functions documentation:

 If the path points to a symbolic link, the notification handle is created for the target. If an application has registered to receive change notifications for a directory that contains symbolic links, the application is only notified when the symbolic links have been changed, not the target files.

Translation: FindFirstChangeNotification won’t shout when a file inside a directory junction changes. And unfortunately, that leaves OneDrive in the dark. 🙁

Posted in OneDrive | Tagged , , , , | Leave a comment

Essential Windows Services: SysMain

SysMain Service

What is SysMain?

SysMain is a Windows Service that monitors the applications running on your computer and tries to improve their performance over time.

For example, if SysMain notices that you run Microsoft Excel frequently, it may automatically place Excel in your computer’s memory. And with Excel already loaded into RAM, the program will come up on your desktop much faster when you actually open it.

The end result is that by anticipating what you’re likely to do soon, SysMain can make your computer seem faster than it is.

The service’s display name is SysMain and it runs as LocalSystem inside the service host process, svchost.exe. By default, the service is set to start automatically when your computer boots:

SysMain Windows Service

Note that in previous version of Windows (before Windows 10 18H2), SysMain was called Superfetch. Microsoft changed the name because future versions of the service will likely do much more than simply caching frequently used programs in memory.

Why is SysMain using so much CPU and RAM?

As mentioned, SysMain’s goal is to speed things up by preparing key applications before you actually need them. Doing so makes your applications load faster.

But the downside of that approach is that SysMain uses system resources before necessary — without your explicit consent/request.

Let’s go back to our Excel example, where SysMain loads Excel into memory before you launch the program. The truth is that when SysMain loads Excel, the service uses CPU and memory to complete that task. And if you happen to be using another application when SysMain is doing its work, your PC may appear sluggish — or even unresponsive.

Fortunately, SysMain won’t bog down most modern PC’s. When there are ample amounts of CPU and RAM, you won’t even notice the Windows Service helping you in the background.

The trouble comes up when your RAM and CPU are limited. In those situations, SysMain is constantly competing with the interactive user for precious resources, and that can make your machine appear slower than it is!

Is it OK to disable the SysMain Windows Service?

Yes. SysMain isn’t an essential system process and you can safely disable it.

Indeed, if your PC suffers from “random spikes” in CPU or RAM, you should see if turning off SysMain reduces or eliminates the problems.

Furthermore, a common bit of advice is to disable SysMain whenever your computer has a fast hard drive. In that situation, pre-loading applications into RAM only saves you a few milliseconds. For example, you probably won’t even notice the small speedup that SysMain provides if you’ve got a speedy solid-state drive (SSD).

However, one bit of advice if you disable SysMain. Because it’s possible that SysMain will deliver significant speedups in future versions of Windows, be sure to reevaluate the service as Microsoft improves its operating systems.

Questions? Problems?

If you would like to know more about the SysMain service, or you have a specific problem, please feel free to get in touch. We will do our best to help you!

Posted in Windows Services | Tagged , , , , | Leave a comment

How to Turn Off Files On-Demand in OneDrive

How to Turn Off Files on Demand in OneDrive

What is OneDrive Files On-Demand?

Files On-Demand saves space on your hard drive by “lazily” downloading the contents of your files from OneDrive only when necessary.

With Files On-Demand, all your files are actually listed on your computer. And as you can see below, each file displays the cloud icon in the status column indicating that it’s online-only:

Online-only files

To be clear, an online-only file does not have its contents downloaded onto your hard drive. You can think of it as a shell — a placeholder for the “real” file in the cloud.

The great thing is that online-only files take up virtually no space on your hard drive. And that’s true regardless of the size of your files in the cloud. As a result, if all your files are online-only, your local OneDrive folder will be tiny — even if you have many gigabytes stored online.

Note that when you first setup the OneDrive desktop application, Files On-Demand will be active by default. All your files will be online-only:

Files On-Demand is active by default

We’ll show you how to change that below.

What’s the problem with online-only files?

While Files On-Demand is great at saving space, it has one major downside. Whenever someone tries to access an online-only file, the OneDrive desktop application must be running to download the file’s contents.

If OneDrive isn’t running, any attempt to work with an online-only file fails with a cryptic error:

Error when accessing an online-only file

And the need to have OneDrive always running can cause unforeseen problems, especially in commercial environments.

For example, let’s say you have OneDrive installed on a server. You’ve shared your OneDrive directory over the network, to allow your users to access the files without having OneDrive installed.

Everything works well when your server is on and OneDrive is running. Your users can access all files just fine — even the ones that are online-only.

However, if OneDrive.exe is not running on the server — maybe because the server rebooted and you didn’t log in yet — your users won’t be able to access the online-only files. Their programs will fail in strange ways, like Adobe Acrobat did when we tried to open an online-only PDF file:

Acrobat cannot open an online-only PDF file

It’s easy to see how the inability to get to the files could cause head-scratching and frustration!

Fortunately, it’s easy to avoid those problems. Simply turn off Files On-Demand.

Disable Files On-Demand and make OneDrive download all your files to your computer

To turn off OneDrive Files On-Demand:

  1. Click the OneDrive tray icon to summon the tray window. From there, click the gear in the upper right and choose Settings from the menu:

    Open OneDrive Settings
  2. In the Sync and Backup section, scroll down and expand Advanced settings.

  3. Under Files on Demand, click Download all files:

    Files On-Demand Settings: Download all files
  4. Finally, click Continue to confirm that you want OneDrive to download all your files:

    Confirm download all OneDrive files

After a few minutes (or hours if your OneDrive is immense), all your files will be available on your hard drive. You’ll be able to access them without issue — even when the OneDrive desktop application isn’t running.

Posted in OneDrive | Tagged , , | Leave a comment

6 Reasons Why AlwaysUp is the Best Tool to Run Multiple Applications as Windows Services

AlwaysUp is the Best Tool for Running Multiple Applications as Windows Services

Most service wrappers focus on a very basic task: installing a single application as a Windows Service. In doing so, they provide little or no support if you need to run several applications when your computer boots.

Understanding that some people need to convert more than one program, we’ve worked hard to ensure that AlwaysUp does a great job managing multiple applications as services. Indeed, there is no limit on the number of applications you can run in AlwaysUp. You can install 1 or 100 — it’s up to you.

Anyway, let’s review the top six reasons why AlwaysUp is your best choice when you need to create many Windows Services.

Reason #1: You can manage all your applications in a friendly, intuitive console

Free alternatives like Microsoft Srvany will install any application as a Windows Service. And others have a friendly GUI that makes installation a mostly point-and-click affair.

However, not many tools provide a console that allows you to monitor, manage and update your applications after they have been installed as services.

With those others, you’ll need to rely on the Services application if you wish to start, stop or update your application. And even though Services is a great little app, it’s going to display your new services mixed in with the nearly 100 installed by Microsoft. That makes it very difficult to work with your own.

In contrast, AlwaysUp makes it easy to manage your new services. The console lists all the applications you have installed and allows you to work with them individually or as a group.

For example, here we have AlwaysUp happily managing 10 applications: Dropbox, OneDrive, and a few Java servers:

AlwaysUp managing 10 applications

It’s easy for you to see which applications are running and which are stopped.

And when you’re ready, key information about each program is a mouse-click away:

AlwaysUp showing OneDrive Information

Furthermore, with the AlwaysUp console you can:

  • Operate on a batch of applications, all at once;

  • Sort the table — by name, application path or state;

  • Hide disabled apps (ones that cannot be started);

  • Search, to show only the entries matching the text you entered;

  • Tag applications, to enable grouping and filtering;

  • View applications as large icons, small icons, or as a simple or detailed list.

We’ll cover some of those capabilities and the advantages they offer in the next sections.

Reason #2: You can start, stop, restart or update several services together

The AlwaysUp console supports multiple selection. As such, you can use the standard Shift and Ctrl key combinations to select multiple application rows.

For example, here we’ve chosen all the java servers that are running:

Java applications running are selected

And with that subset selected, we can choose to restart them all at once from the “Application” menu:

Restarting the Java applications selected

Note that you can perform several operations on the group as a set. With a single action, you can:

  • Stop the selected applications;

  • Start them all;

  • Restart the entire group in your session;

  • Change the startup type for each entry;

  • Apply tags to the applications, as a unit;

  • Export each app to a portable XML file.

Those functions are all available from the toolbar and in the “Application” menu.

Reason #3: You can group and filter your applications using tags

Tagging is an organizational feature that allows you to group your applications in any way you like.

For example, you will notice in the screenshots above that the Dropbox and OneDrive entries have a tag named “cloud”. To focus on just those two applications and temporarily eliminate the rest from the view, we would:

  1. Activate the Filter Pane from the View menu;

  2. In the Filter Pane, check the Show only applications with tag box;

  3. Choose the “cloud” tag from the list.

Show applications with the cloud tag

From there, we could simply select both applications and start, stop or restart them.

As you can see, tags make it easy (and efficient) to work with a subset of your applications as a unit.

Reason #4: You can easily export and import your applications “in bulk”

AlwaysUp makes it easy for you to move your applications between your computers. Simply export each application from the “source” PC and import it onto the “destination” machine to recreate it there.

The Bulk Import Wizard provides an optimal experience when you have to import multiple apps. Instead of making you stand up each application separately, the wizard requests common information (like your Windows password) once and applies it to all the applications being imported. The end result is the speedy recreation of all your services on your new computer.

Easily import your Windows Service applications into AlwaysUp

Importing with the wizard can be a real time saver when you’re moving dozens of apps!

Reason #5: You can update your view to fit more applications on your screen

Customers running north of 50 applications in AlwaysUp tell us that screen real estate is a precious commodity. It’s important for them to have all their apps visible in the window — without constantly having to scroll or page around to see them all.

Over the years, we’ve made many improvements to AlwaysUp targeted at those space-conscious customers. For example, you can use the “View” menu to hide the:

  • Toolbar of buttons at the top;

  • Status bar at the bottom;

  • List headers that summarize the applications you are running.

By removing some of those visual components, you can dedicate maximum space to the list of applications:

Hide components to show more applications

And if you really want to pack them in and show 100+ applications, you can switch to small icons (via the “View” menu):

View small icons to show even more applications

As you can see, AlwaysUp makes it super easy to show as many of your applications on screen as possible.

Reason #6: We’ve been making improvements in this area for almost 20 years

Like many of the other service wrappers, AlwaysUp started out with a focus on installing a single application as a service. After all, that’s what most folks want to do at first.

But over the years, our customers have shown us that they are much more ambitious. Indeed, we have a few of corporate clients that use AlwaysUp to manage over 100 applications on a single server!

We’ve learned a lot from those customers. And we consistently try to improve AlwaysUp to meet their strenuous demands.

Most recently, our developers tuned underlying algorithms to ensure that our code performs efficiently when orchestrating many applications. Those efforts reduced CPU usage by a whopping 45% in some circumstances.

AlwaysUp running many applications

And we won’t stop there. We’ll continue to improve the software and make it even easier for you to manage multiple programs. Be sure to let us know if you have any great ideas. 🙂

Posted in AlwaysUp | Tagged , | Leave a comment