Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 22 2018 12:49
    per-samuelsson labeled #4643
  • May 22 2018 12:48
    per-samuelsson labeled #4643
  • May 22 2018 12:48
    per-samuelsson opened #4643
  • May 22 2018 12:43
    miyconst commented #4642
  • May 22 2018 12:42
    miyconst assigned #4642
  • May 22 2018 12:39
    per-samuelsson commented #4642
  • May 22 2018 12:34
    miyconst labeled #4642
  • May 22 2018 12:34
    miyconst commented #4642
  • May 22 2018 12:33
    miyconst labeled #4642
  • May 22 2018 12:21
    bigwad commented #4638
  • May 22 2018 12:21
    per-samuelsson edited #4642
  • May 22 2018 12:21
    per-samuelsson commented #4642
  • May 22 2018 12:21
    per-samuelsson labeled #4642
  • May 22 2018 12:21
    per-samuelsson labeled #4642
  • May 22 2018 12:20
    per-samuelsson opened #4642
  • May 22 2018 12:02
    per-samuelsson commented #4638
  • May 22 2018 10:45
    k-rus commented #4641
  • May 22 2018 10:19

    bigwad on 121

    (compare)

  • May 22 2018 10:19

    bigwad on develop

    Add blocking debugger notificat… (compare)

  • May 22 2018 10:03

    bigwad on 121

    Add blocking debugger notificat… (compare)

Martin Törnwall
@mtornwall
As for Linux support, Starcounter doesn't run on Mono. The .NET parts might, but there's a lot of native code underneath. A release that will support the Linux+coreclr platform is supposed to be coming in 2016, but since I'm not a Starcounter employee I can't speak to when.
PatrickStudi
@PatrickStudi
thanks @mtornwall, I read up on SC github and realized mono support is in the 3.x milestone quite far down the road.
You run on a virtualized machine on Azure right? Any issues with that?
Dan Skatov
@dan31
@mtornwall thanks for an excellent follow-up :) @PatrickStudi, we have really exceptional users! To add to @mtornwall feedback, we recommend at least 2 cores and 8 GB RAM. We do not recommend 1-core instances for a real-world usage. Good default choice for a storage is HDD. Modern HDDs can burst terabytes of sequential writes in seconds. You can read more on that choice here: http://starcounter.io/guides/tools/run-starcounter-in-production/. However, in AWS the HDD doesn't come inside your instance, hence you might notice a need to move to SSD if you have write-intense applications with +70% writes.
Dan Skatov
@dan31
@PatrickStudi We target native Microsoft's dnx over Mono. Our plans on releasing a dnx version are tightly connected to their roadmap: https://github.com/aspnet/Home/wiki/Roadmap. Their decision this year is to let in more time to have all bits working together: https://blogs.msdn.microsoft.com/webdev/2016/02/01/an-update-on-asp-net-core-and-net-core/. Hence we will get back to you once the dnx roadmap is clarified and becomes less moving target. Currently we focus our development on features for our Windows users, such as a replication module, and numerous of usability improvements.
PatrickStudi
@PatrickStudi
@dan31 Thanks Dan, excellent info! For now running on Windows is not a problem but in the long run *nix support will matter.
Dan Skatov
@dan31
This message was deleted
Dan Skatov
@dan31
@PatrickStudi We are currently running a couple of AWS instances for our own things. We have t2.medium for app playgrounds and c4.xlarge for a download server. The latter we had to move to c4.xlarge since it prepares installers (not SC-related stuff, like packing, signing etc) and produces a considerable load on the machine. In order to make this preparations less a bottleneck and let tens of downloads simultaneously without a noticeable slowdown, we moved the original t2.large to c4.xlarge. However, we are considering to move our servers from AWS to several dedicated/VPS machines. In Sweden we have a provider called GleSYS who provides VPS and dedicated servers for a decent price in Stockholm and London. Going that path of "non-cloud" machine, one have to cater for backups and failover on his own, I don't see a problem with it, especially considering the forthcoming Windows Server 2016 with sync and async storage replica on board. We also have a successful usage cases of Hetzner dedicated servers among our customers, where you can have a Windows machine with 48 Gigs of ram + 4 Tb HHD + 30 Tb channel per month worth only 70 euros per month. Perhaps, a strong benefit of AWS when you should afford AWS costs is the ability to move instances easily between regions. When you need a machine in the US (to reduce latency for the local customers), it takes you 30 mins only on AWS to have a clone of your European instance. If you are going to utilise Starcounter in production in a long run, we recommend to use either dedicated server or your own server/colocation, it will pay back in a matter of a year. AWS/Azure machines work flawlessly as well, your only consideration is total cost of the machine ownership. More on tuning failover/backups today with Starcounter you can read on http://starcounter.io/guides/tools/run-starcounter-in-production/. In future versions we are going to provide simpler tools with Starcounter out of the box to handle these scenarios.
PatrickStudi
@PatrickStudi
Great! We use Glesys as well as Amazon so that gives me confidence we won't be locked in or trip up on the hardware. Thanks again
Martin Törnwall
@mtornwall
@PatrickStudi I haven't had any serious issues with Starcounter on Azure so far, but to be fair my serivces haven't been under any signficant load. Nevertheless they have been running flawlessly with acceptable uptime (~ 99.9%) in spite of my questionable software upgrade practices :)
There have been no instances whatsoever of downtime caused by Starcounter
Ersin Tarhan
@ersintarhan
Hello guys. How i can implement Sql's MERGE logic to Starcounter with best performed?
Ruslan Fomkin
@k-rus
Hi @ersintarhan MERGE can be implemented with SELECT statements and iterating the results and inserting new raws in C# code. The performance will mainly depend on your SELECT statements. There is performance penalty in mixing SQL and C# logic in Starcounter, since it is not an ORM. If you need more elaborated answer, welcome to submit your question on starckoverflow, where it suits well, or on our GitHub tracker.
O-lexey
@O-lexey
Dear friends, could you help me with Starcounter on Windows Server 2016? Everything works well on my desktop Windows 10. I have done a clean installation of Windows Server 2016 Standard. And then Starcounter, without any errors. But when I try to start: "ScErrNetworkGatewayTerminated (SCERR10021): The server detected that the network gateway executable (scnetworkgateway.exe) unexpectedly terminated."
Dan Skatov
@dan31
Hello @O-lexey! @alemoi, please have a look (I don't think we have any customers running on Windows Server 2016 yet), maybe this is something you are already aware of on fresh installations of Windows Server?
O-lexey
@O-lexey
Also, I should mention, that Starcounter Administrator works well, I can create databases, download apps, install them, delete. But not run. Trying to start "Hello world" : System.Exception: ScErrHandlerAlreadyRegistered (SCERR13003): This handler has already been registered. Can't register URI handler "GET /sc/db/{?}/{?}" on port 8080. This handler is already registered.
Konstantin
@miyconst
@O-lexey please check whether port 8080 is occupied by any other program.
Per Samuelsson
@per-samuelsson
Ans @O-lexey, if the advice from @miyconst doesn't help, do you mind if we open an issue for this on our tracker over at https://github.com/Starcounter/Starcounter/issues? It might affect and interest other users as well I'm thinking.
O-lexey
@O-lexey
I'm checking, netstat says me, that 8080 is bind to ... scnetworkgateway.exe
Let
Let's I do some more investigations
O-lexey
@O-lexey
Seems, it's my mistake, on Windows 10 Starcounter runs its service manually by default, and I used to start it by hand. On Windows Server 2016 it starts server automaticaly by default, and I tried to start another Starcounter instance - that's was a mistake.
Per Samuelsson
@per-samuelsson
@O-lexey, thanks for giving that feedback. We are aware of the problem that it's a big diffuse on how Starcounter backend services are running in different contexts. It's currently dependent on whether you install the Visual Studio extension or not - if you install that, we assume a developer machine, and we run Starcounter backend services in user mode. If you don't, we assume a system / production environment, and we run Starcounter as a service by default. It's hard for users to realize this and we will try to improve on that in time. Sorry you got hit by it. :worried:
@O-lexey, if you are interested in reading more, we have some discussion in this issue: Starcounter/Starcounter#3852
hossainruetcse
@hossainruetcse
how can I use starcounter with visual studio 2013?
Per Samuelsson
@per-samuelsson
@hossainruetcse, we normally just focus on keeping real support for the latest 2 versions of visual studio (i.e now being 2015 and 2017) for our Visual Studio extension, but you can use Starcounter without that, just that debugging and scaffolding projects require a few more manual steps
Per Samuelsson
@per-samuelsson