search for: xlarg

Full_Name: Morten Welinder Version: 2 OS: Solaris/space/gcc2.95.2 Submission from: (NULL) (65.213.85.217) I changed src/nmath/standalone/test.c to read: --------------------------------------------------------------------------------- #define MATHLIB_STANDALONE 1 #include <Rmath.h> #include <stdio.h> int main() { double x; for (x = 99990; x <= 100009; x++) printf

...values Large 3 > > dfValues <- data.frame(tblValues) > dfValues values Freq 1 Large 3 2 Small 1 > subset(dfValues, Freq > 2) values Freq 1 Large 3 > > factorValues <- factor(values, levels=c("Small","Medium","Large","XLarge")) > data.frame(table(factorValues)) factorValues Freq 1 Small 1 2 Medium 0 3 Large 3 4 XLarge 0 Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Sep 21, 2017 at 6:01 AM, Ferri Leberl <ferri.leberl at gmx.at> wrote: > > Dear all,...

Dear all, ftable produces a list of the frequencies of all occuring values. But how about the occuring values? How can I retrieve a list of occuring values? How can I retrieve a table with both the list of occuring values and their respective frequencies? Thank you in advance, Yours, Ferri

Hi, We have our rails application running on AWS. we have two application servers and one database(postgres) server of C1.xlarge <http://aws.amazon.com/ec2/instance-types/> AWS instance type. Our passengermaxpoolsize is set to 30. And postgresql max connection limit is 100. Recently we found that when we got nearly 700 request per minute, our application created nearly crossed the max connection limit of postgres...

I have been tweaking and researching for a while now and can't seem to get "good" performance out of Gluster. I'm using Gluster to replace an NFS server (c1.xlarge) that serves files to an array of web servers, all in EC2. In my tests Gluster is significantly slower than NFS on average. I'm using a distributed replicated volume on two (m1.large) bricks: Volume Name: ebs Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Bric...

...the same values for these parameters in each file): Approximate values for some important machines are: it NSIG ENTEN ENSIG [...] IEEE (IBM/XT, SUN, etc.) (D.P.) 53 16 1.0D+308 1.0D+16 [...] RTNSIG ENMTEN XLARGE [...] IEEE (IBM/XT, SUN, etc.) (D.P.) 1.0E-4 8.90D-308 1.0D+4 [...] Is there some reason for using different values in bessel_j.c than in bessel_l.c? Or is this just a bug? ;^) -Greg PS: Where is DBL_EPSILON defined, and what is its value? -.-.-.-.-.-.-.-...

...the same values for these parameters in each file): Approximate values for some important machines are: it NSIG ENTEN ENSIG [...] IEEE (IBM/XT, SUN, etc.) (D.P.) 53 16 1.0D+308 1.0D+16 [...] RTNSIG ENMTEN XLARGE [...] IEEE (IBM/XT, SUN, etc.) (D.P.) 1.0E-4 8.90D-308 1.0D+4 [...] Is there some reason for using different values in bessel_j.c than in bessel_l.c? Or is this just a bug? ;^) -Greg PS: Where is DBL_EPSILON defined, and what is its value? -.-.-.-.-.-.-....

Hi, the updated Amazon Web Service AMI (ami-4ac6653d) has a serious bug. It is not possible to resize a disk after creating a new volume with a size greater than 8GB. resize2fs does nothing. The previous AMI worked perfectly but is no longer available. This bug is a show stopper for using CentOS on AWS. Regards, Thorsten PS: It would also be great to have a CentOS 6 AMI with HVM