1 core, 2 cores, 2GB RAM, 4GB RAM, the question is only relevant if you
have no expandability. Select your software, take its recommendation, and
probably a little more, then make sure you can grow as needed.
Here is an example.
Let's say you go to AWS, get a server that is large enough to
Hi,
I am wondering what your opinion is on cores and RAM when using a VPS.
I am thinking about this in the context of Drupal and Magento, both of
who are resource hogs.
I was told more RAM is much more valuable on a VPS than is the number of
cores.
I'm assuming 4G of RAM is enough to not
I almost always create 2 cores for most minimum configurations when
available in any virtual environment. but in the case of a VPS it really
matters how well your stack handles multi-threading and if you expect to
have enough load to saturate a core.
On Tue, Sep 8, 2015 at 1:01 PM, Keith Smith
I don't know that I would want to run a production site with Magento and
Drupal with less than 4gb of ram. The cores = more visitors concurrently
to your website. Unless very well designed, mysql/mariadb threads will
only use a single core per query, so one user on the site could
I am looking for a way to stream an RTSP stream to a bunch of people
internally, so kind of a locally hosted live CDN. I have looked into
trying it with VLC but it seems to only stream files.
Here are a couple of the base requiremnets that I need to meet:
1. locally hosted
2. CLI to add/remove
I would also say at least 2 cores and 4GB RAM. We have many clients that try to
run 1 core with bare minimum RAM and their VPS does not run well. Especially
when it's magento or opencart.
Jason
Sent from my iPhone
> On Sep 8, 2015, at 1:26 PM, Kevin Fries wrote:
>
> 1
Ah, different media. I guess people do
watch video stuff.
You talking personal or business?
Yes, done some with like digital signage, live video feeds, etc.
I'm not sure if any non-commercial encoders out there, but we used
an appliance
The Live555 Proxy Server looks to be a good solution so far.
Thanks Ed
On Tue, Sep 8, 2015 at 4:30 PM, Ed wrote:
> look in your repo for live555
> http://www.live555.com/
>
> also - depending on your use case try MediaGoblin
> http://mediagoblin.org/
>
> On Tue, Sep 8, 2015 at
Hi all,
Thanks for your replies James and Hans. I've included some responses in
the bellow email:
> moin moin TJ,
>
> what James said in regards to debugging ntp :).
>
Ill check on these step tickers, but my understanding was that the -g
option should take care of that. Can I put in sdout's in
On Tue, 8 Sep 2015 14:41:04 -0700
Shawn Badger wrote:
> I am looking for a way to stream an RTSP stream to a bunch of people
> internally, so kind of a locally hosted live CDN. I have looked into
> trying it with VLC but it seems to only stream files.
> Here are a couple of
Assumptions:
1) you need audio and video (as RTSP is just a control protocol, either or
both could be the case)
2) You do not need a proprietary input codec (RTSP does not set codec, that's
a stream detail)
3) Any reasonably common container/codec combination will work for your
clients
Icecast - not just for audio!
On Tue, Sep 8, 2015 at 5:21 PM, Steve Litt wrote:
> On Tue, 8 Sep 2015 14:41:04 -0700
> Shawn Badger wrote:
>
>> I am looking for a way to stream an RTSP stream to a bunch of people
>> internally, so kind of a locally
So I'm thinking there has to be some sort of concurrent startup runlevel
issue. Not really sure how to adjust this, but do you see any place in
that init script that could cause this or something left out of the
dependencies or something? Here's the first bit of the init.d again:
### BEGIN INIT
Joesph,
The stream can be either encoded mp4 or H.264 so since either of those can
be played in most modern browsers no need to re-encode the video.
The thought is that when the video is needed by the particular internal web
page the server will launch the vpn client to connect to the site then
Wow, that is still around
On Tue, Sep 8, 2015 at 5:39 PM, Ed wrote:
> Icecast - not just for audio!
>
> On Tue, Sep 8, 2015 at 5:21 PM, Steve Litt
> wrote:
> > On Tue, 8 Sep 2015 14:41:04 -0700
> > Shawn Badger wrote:
> >
> >> I am
This all depends on the load your planning on putting on the web server.
Assuming you are using Apache as your web server, Apache forks a new
process (thread) for every web request. Drupal uses (my experience)
between 20MB - 70MB per process. Total capacity (number of processes or
MaxClients)
If you missed that one here is another opportunity:
Invite
17 matches
Mail list logo