Running Background Jobs

Search…
Introduction
Starcounter maintains its own thread pool. Most of Starcounter API may be called only from a thread from the Starcounter thread pool. Among such APIs are: methods from Starcounter.Db class, methods from Starcounter.Request class etc. Safer to regard all APIs from Starcounter namespace as required to be called on a Starcounter thread, unless explicitly stated otherwise. Starcounter assures that an application Main, typed JSON event handlers and HTTP-handlers registered with the Handle API are called on a Starcounter thread. In other situations, like your code is running on separately created .Net threads or on .Net thread pool, you have to schedule a task on Starcounter thread pool using Scheduling.RunTask in order to be able to use Starcounter API. You can call Scheduling.RunTask while on a .NET or Starcounter thread. StarcounterEnvironment.IsOnScheduler is another method that can be called on any thread, it tells you if the current thread is a Starcounter thread.
Example of running a background job and accessing database:
1
using System.Threading;
2
using Starcounter;
3
​
4
namespace StarcounterSampleApp
5
{
6
    class Program
7
    {
8
        static void Main()
9
        {
10
            ThreadPool.QueueUserWorkItem(o => { RunForever(); });
11
        }
12
​
13
        static void RunForever()
14
        {
15
            while (true)
16
            {
17
                Scheduling.RunTask(async () =>
18
                {
19
                    await Db.TransactAsync(() =>
20
                    {
21
                        // Access database.
22
                    });
23
                }).Wait();
24
            }
25
        }
26
    }
27
}
Copied!
Basic Information About Scheduling
Tasks scheduled by Scheduling.RunTask as well as ready-to-call handlers make a queue of ready tasks. Then Starcounter picks tasks and runs them on a free thread from the thread pool. By default Starcounter thread pool hosts number of threads equal to number of CPU cores. It allows to maximize throughput by avoiding unnecessary context switches. But what if user code happens to block on IO or synchronization? Starcounter is able to detect such condition and launch an additional thread, so that queue processing doesn't stall. To maximize throughput, don't rely on thread pool scaling. Better to avoid blocking calls and use async IO whenever possible. To put a task in a queue, the Scheduling.RunTask should be used:
1
Task RunTask(Action action)
2
Task RunTask(Func<Task> action)
Copied!
where action is a procedure to execute on a Starcounter thread. Task being returned is a regular .Net task object which can be used in any appropriate context as any regular .Net task.
Task scheduling and async/await
Starcounter currently doesn't provide specialized .Net synchronization context. As a consequence if you're programming asynchronous delegate and use async/await in your code, the continuation code after await gets scheduled on a regular .Net thread pool thread, not on a Starcounter thread. It means that Starcounter API can't be directly used in a continuation. Instead, one should manually schedule continuation with Scheduling.RunTask. Below is an example demonstrating this. It uses delayed Response. Note also the use of Db.TransactAsync - it's needed because Db.Transact is also a blocking call that can increase number of threads in Starcounter thread pool.
1
[Database]
2
public class Person
3
{
4
    public String Id { get; set; }
5
}
6
class Program
7
{
8
​
9
    static void Main()
10
    {
11
​
12
        Handle.GET("/hello/{?}", (Request req, Int32 id) => {
13
​
14
            // As we are on Starcounter thread already, we can create a database object.
15
            // Notice that we use `Db.TransactAsync` here. Read about it in a separate article.
16
            Db.TransactAsync(() => new Person() { Id = id.ToString() });
17
​
18
            // Now we run an async task that will return the response later.
19
            DoSomethingAsync(req, id);
20
​
21
            // Indicating that HTTP response will be returned later.
22
            return HandlerStatus.Handled;
23
        });
24
    }
25
​
26
    // Async call that does some await and performs database operations after.
27
    static async void DoSomethingAsync(Request req, Int32 id) {
28
​
29
        // Now using async to simulate some long operation using await statement.
30
        await Task.Delay(10000);
31
​
32
        // Since this is not a Starcounter thread now, so we need to schedule
33
        // a Starcounter task so we can do our database operations.
34
        await Scheduling.RunTask(() => {
35
            // Querying the person.
36
            var person = Db.SQL<Person>("SELECT p FROM Person p WHERE p.Id = ?", id.ToString()).FirstOrDefault();
37
​
38
            // Doing some database operations.
39
            // Notice that we use `Db.TransactAsync` here. Read about it in a separate article.
40
            Db.TransactAsync(() => person.Id += id);
41
        });
42
​
43
        // Now in continuation we need to perform some other Starcounter operations
44
        // therefore we need to use `Scheduling.RunTask` again.
45
        await Scheduling.RunTask(() => {
46
​
47
            // Finally returning the response.
48
            Response resp = new Response() {
49
                Body = "Done with object " + id
50
            };
51
​
52
            req.SendResponse(resp);
53
        });
54
    }
55
}
Copied!
Exceptions in scheduled tasks
Unhandled exceptions in scheduled tasks are logged to the Administrator log. Besides of this fact, exception handling is identical to that of a regular .Net task.
Using Transactions
Commit Hooks
Last modified 3yr ago
Copy link
Contents
Introduction
Basic Information About Scheduling
Task scheduling and async/await
Exceptions in scheduled tasks