Displaying 9 results from an estimated 9 matches for "relaibility".
Did you mean:
realibility
2013 Mar 16
1
Client ... has fallen too far behind, removing - but only when listening to a relay, not when listening to fallback
....xx.xx is my listening IP address (server A and B being
remote, server B with a good internet connection (Amazon EC2), and
Server A having a more patchy internet connection - hence the reason
for using a relay with fallback.
My internet connection is reliable ADSL, the stream is 64k, and given
the relaibility when on fallback, it doesnt appear credible that the
listening connection has a problem. Any advice on where to start
looking much appreciated. Searches of the mailing list haven't shouwn
anything that appears relivant.
Regards
Nathan
2013 Jun 06
0
[LLVMdev] Enabling the vectorizer for -Os
Hi,
Thanks for the feedback. I think that we agree that vectorization on -Os can benefit many programs. Regarding -O2 vs -O3, maybe we should set a higher cost threshold for O2 to increase the likelihood of improving the performance ? We have very few regressions on -O3 as is and with better cost models I believe that we can bring them close to zero, so I am not sure if it can help that much.
2013 Jun 05
0
[LLVMdev] Enabling the vectorizer for -Os
On 5 June 2013 13:32, David Tweed <david.tweed at arm.com> wrote:
> This is what I'd like to know about: what specific potential to change
> results have you seen in the vectorizer?
>
No changes, just conceptual. AFAIK, the difference between the passes on O2
and O3 are minimal (looking at the code where this is chosen) and they
don't seem to be particularly amazing to
2008 Mar 24
2
Theora performance
Hi list,
I just came across this site:
http://web.mit.edu/xiphmont/Public/theora/demo.html
I was wondering are these issues being addressed or will be addressed before
the 1.0 release?
Theora is like the only open sourced free code people can use, i will be
nice if it performs close to other libs.
please keep up the good work!
-------------- next part --------------
An HTML attachment was
2005 Mar 03
1
A probably silly thought but...
...> >
> > cheerz
>
> DRBD would not help this problem. As you say the filesystem
> corruption would immediately be duplicated to the alternate server.
>
> OTOH a good journelled filesystem combined with dual-power supplies
> and dual ups's should have a very high relaibility rate. EXT3 seems
> to get mentioned as the most reliable linux filesystem, so go with
> that if reliability is your top concern.
>
> Greg
> --
> Greg Freemyer
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/li...
1999 Feb 26
3
Win95 won't work with Samba 2.0.2
Hmmm... I've sent a couple of questions to the list recently, with
no responses. Are my messages getting out?
Since upgrading to 2.0.2, our Win95 boxes are having problems
accessing shares. WinNT works perfectly. Win95 worked fine
with 1.whatever, but now it can only see files that are actually in
the share directory. It can see subdirectories of the share, but
they appear as empty
2013 Jun 06
2
[LLVMdev] Enabling the vectorizer for -Os
On Wed, Jun 5, 2013 at 5:51 PM, Nadav Rotem <nrotem at apple.com> wrote:
> Hi,
>
> Thanks for the feedback. I think that we agree that vectorization on -Os
> can benefit many programs. Regarding -O2 vs -O3, maybe we should set a
> higher cost threshold for O2 to increase the likelihood of improving the
> performance ? We have very few regressions on -O3 as is and with
2010 Jun 25
4
[CRON] Right way to restart Asterisk and Zaptel?
Hello
About every three months, my dad's little Asterisk server that handles
his business phone line with an OpenVox PCI card stops taking calls.
To check if it's the cause, I'd like to run a CRON job every night to
restart Zaptel and Asterisk.
Before I go ahead, I'd like to know if I can just send the following
commands, or if there are issues I should know about:
2013 Jun 05
15
[LLVMdev] Enabling the vectorizer for -Os
Hi,
I would like to start a discussion about enabling the loop vectorizer by default for -Os. The loop vectorizer can accelerate many workloads and enabling it for -Os and -O2 has obvious performance benefits. At the same time the loop vectorizer can increase the code size because of two reasons. First, to vectorize some loops we have to keep the original loop around in order to handle the last