search for: 23.17

Dear R users, I have a txt file of the form 10092007 24.62 24.31 24.90 11092007 19.20 23.17 22.10 13092007 24.71 27.33 23.10 14092007 27.33 27.90 24.10 15092007 28.22 28.55 24.30 16092007 28.53 29.24 27.40 17092007 24.19 30.64 26.80 18092007 22.60 20.62 28.40 19092007 8.89 1.70 14.70 20092007 21.27 2.92 17.30 21092007 22.38 24.72 8.80 22092007 23.94 24.73 20.40 23092007 25.33 25.12 22.60

Dear R-users, I have to deal with (txt) files of the form 10092007 24.62 24.31 24.90 11092007 19.20 23.17 22.10 13092007 24.71 27.33 23.10 14092007 27.33 27.90 24.10 15092007 28.22 28.55 24.30 16092007 28.53 29.24 27.40 17092007 24.19 30.64 26.80 18092007 22.60 20.62 28.40 19092007 18.89 21.70 14.70 20092007 21.27 22.92 17.30 21092007 22.38 24.72 18.80 22092007 23.94 24.73 20.40 23092007 25.33

Hi, is this ok for a database server, or do I need to turn the memory allowance down? The machine has 48GB and mariadb is allowed about 40. The machine is a dedicated database server. Mysql seems to go up to what top says is virtually allocated under some circumstances; I don?t know what mariadb does. I don?t want anything get killed because memory runs out. Swap should prevent that anyway,

> Michael Grimm <trashcan at odo.in-berlin.de> kirjoitti 9.5.2015 kello 23.17: > > Hi ? > > Timo Sirainen <tss at iki.fi> wrote: > >> Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. > > 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed Dovecot hg requires bash

On 11/04/2017 10:05 AM, hw wrote: > > Hi, > > is this ok for a database server, or do I need to turn the memory > allowance > down?? The machine has 48GB and mariadb is allowed about 40. The > machine is a dedicated database server. > > Mysql seems to go up to what top says is virtually allocated under some > circumstances; I don?t know what mariadb does.? I don?t

Disk cache is not recommended for databases servers. it'll slow down the performance. More ram equals more performance. This link help me understand memory usage on linux. https://www.linuxatemyram.com/ Basically you need yo worry about free memory is close to 0 used memory is close to total available memory (or "free + buffers/cache") has enough room (let's say, 20%+ of

Hi Carsten, yes, your emails take up my morning, too. :-) <p><p>Am Mo, 2003-11-24 um 23.17 schrieb Carsten Breuer: > Hi Ulrich, > > > Well, i don't know if we speak of the same ... The quality is ok, but > > the encoding of a PCM frame on the tested machine took 2ms, which (if > > the PCM frame is 7ms in length) means the machine can only encode three

Hello, "doveadm auth user password" may be scripted without a glitch. But this comes with the usual problem of a "ps" command showing the password, which may be especially annoying in case of a single-letter typo: the almost correct password is then visible for about two seconds... Clearing the password argument (zeroing it) in doveadm-auth.c, in the hope to reduce the window

I'm preparing to set up a new set of directors on dovecot-ee-2.1.10.3-1, but would prefer to do this a bit gradually. Will it be OK to set up a ring of directors with 2x dovecot-ee-2.1.10.3-1 and 2x dovecot-2.0.14 ? -jf

We're using dovecot (via LMTP) as a backup for all incoming mail. I upgraded from 2.3.6 to 2.3.7 on the 12th: 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic 2:2.3.7-8~bionic and it seems that 2.3.7 is slower than 2.3.6 -- mail to the backup IMAP box is suddenly taking quite some time to get delivered and is piling up in the queue. doveconf -n: ============

On 15 Jul 2019, at 23.17, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > * Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: >> We're using dovecot (via LMTP) as a backup for all incoming mail. >> >> I upgraded from 2.3.6 to 2.3.7 on the 12th: >> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic 2:2.3.7-8~bionic

Hi Ulrich, > Well, i don't know if we speak of the same ... The quality is ok, but > the encoding of a PCM frame on the tested machine took 2ms, which (if > the PCM frame is 7ms in length) means the machine can only encode three > streams in realtime ... Yes, but this is java. You don't use any threading models and i dont know if you encode from sound card. I also don't

R Help - I'm trying to run a correlation matrix with a covariate of "age" and will at some point will also want to covary other variables concurrently. I'm using the "psych" package and have tried other methods such as writing a loop to extract semi-partial correlations, but it does not seem to be working. How can I accomplish this? library(psych) > set.cor(y =

Hi, We are currently working on revising a journal article that describes our work on pre-allocation scheduling using LLVM and have some questions about LLVM's pre-allocation scheduler. The answers to these question will help us better document and analyze the results of our benchmark tests that compare our algorithm with LLVM's pre-allocation scheduling algorithm. First, here is a

Hello, My question is regarding the interpretation of --stats output and whether I have a performance issue or not. Can the client/server architecture (rsync client on one machine, rsync server on another machine) be far slowlier than a local rsync session ? This is the ouput of an rsync session: date rsync -v --recursive --links --perms --times --group --owner --xattrs --acls --delete

Hi Marco, Thank you for the follow up email. In the line below, do I replace $(lsb-release -cs) with jammy (Ubuntu 22.04) or leave it alone: Add-apt-repository ?deb https://cloud.r-project.org/bin/linux/ubuntu jammy-cran40/? It?s good to know about installations for Bioconductor. I am not currently using it, but I may need it in the future for other projects. Br, Lauren -- Lauren J. Gerber

Yes, keep the $(lsb-release -cs) there. This allows you to change the version of the OS without having to change anything else (for instance we are migrating all of our docker to 24.04 LTS right now, so we only have to modify the FROM entry and all of our Dockerfile will still work). From: Gerber, Lauren J <lauren.gerber at helsinki.fi> Date: Thursday, July 11, 2024 at 2:21?AM To:

Hi Ghassan, this is very interesting, however... > We are currently working on revising a journal article that describes our work > on pre-allocation scheduling using LLVM and have some questions about LLVM's > pre-allocation scheduler. The answers to these question will help us better > document and analyze the results of our benchmark tests that compare our > algorithm with

On Sep 29, 2012, at 2:43 AM, Ghassan Shobaki <ghassan_shobaki at yahoo.com> wrote: > Hi, > > We are currently working on revising a journal article that describes our work on pre-allocation scheduling using LLVM and have some questions about LLVM's pre-allocation scheduler. The answers to these question will help us better document and analyze the results of our benchmark

Lauren, little oversight from my Dockerfile, if you want to follow the CRAN steps and get the R from the cloud.r-project.org server, you want to replace && add-apt-repository -y "ppa:marutter/rrutter4.0" With && add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" The ppa repo is Michael Rutter personal repo