jas14 / amity-apcs-ge-2011

Automatically exported from code.google.com/p/amity-apcs-ge-2011
0 stars 0 forks source link

Multithreading #26

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I don't see anything in the rules that prevents it and this is running on a 
dual core processor, possibly with hyper threading (unlikely, though).  I think 
we should ask them if multithreading would be allowed.

Original issue reported on code.google.com by smd7...@gmail.com on 27 Mar 2011 at 9:05

GoogleCodeExporter commented 9 years ago
"You can do whatever you want with in the solver.java class (as long it is the 
only class submitted)"

We are taking that email with us it is like our golden key for this project.

However, I do not think we should make this multithreaded. One core will 
probably mainly be doing OS stuff so we are really limited at one core, and 
will probably be faster with that.

Original comment by drdaniel...@gmail.com on 27 Mar 2011 at 2:21

GoogleCodeExporter commented 9 years ago
@1 I have no idea what you're thinking, but even if the other is occupied, 
using two is /still/ faster, because you can just pull parts over to the other 
processor it's you're done, unless the spawning of threads is expensive.

that said, we should probably still ask.

Original comment by sreservoir on 27 Mar 2011 at 5:41

GoogleCodeExporter commented 9 years ago
@2 I definitely agree that using two threads should be faster.  The UI won't be 
doing a huge amount of work while we're computing our moves and the spawning of 
threads is somewhat expensive but as long as we're only talking about 
instantiating a few threads, the extra time should be negligible.

I think the two things we should ask are:
1. Are we allowed to use threading in our application?
2. Does the processor this will be running on have hyper threading/How many 
threads are available for use on the computer? (I assume only 2, but still 
worth asking while we're at it)

Original comment by smd7...@gmail.com on 27 Mar 2011 at 7:35

GoogleCodeExporter commented 9 years ago
i assume we have pretty much an infinite number (ik mike its only a couple 
thousand) and when timing they wont even be using the UI.

Original comment by drdaniel...@gmail.com on 27 Mar 2011 at 7:53

GoogleCodeExporter commented 9 years ago

Original comment by drdaniel...@gmail.com on 27 Mar 2011 at 8:25

GoogleCodeExporter commented 9 years ago
Well by number of threads I mean number of threads it would make sense to use.  
Sure, we can create 1000 threads but I think it's most efficient to use as many 
threads as there are cores (times 2 if hyper threading is enabled).

Original comment by smd7...@gmail.com on 27 Mar 2011 at 9:31

GoogleCodeExporter commented 9 years ago
I've already sent one off asking about #1. for #2, I imagine you can create as 
many as you need, as long as it not excessive, because computers are kind of 
fast enough to deal with it nowadays.

@4 and that would be wrong. my computer can handle well in excess of a hundred 
thousand threads doing nothing. it's just not very efficient at time-allocation 
for them.

Original comment by sreservoir on 27 Mar 2011 at 10:12

GoogleCodeExporter commented 9 years ago
Hi Michael,

Thank you for your question!  In the future, please email
CSC.CaseStudy@ge.com (CC'd above) for any case study questions.

I am forwarding this along to them, someone from that team will get back
to you shortly.

Thanks,
Murali & Kristen

Original comment by sreservoir on 27 Mar 2011 at 11:56

GoogleCodeExporter commented 9 years ago
that is a /really useless/ answer. especially considering I was using their 
site form.

Original comment by sreservoir on 27 Mar 2011 at 11:57

GoogleCodeExporter commented 9 years ago
From - Mon Mar 28 08:48:51 2011
X-Account-Key: account2
X-UIDL: GmailId12efc8274c9a0128
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                 

Delivered-To: sreservoir@gmail.com
Received: by 10.42.180.193 with SMTP id bv1cs49469icb;
        Mon, 28 Mar 2011 05:48:52 -0700 (PDT)
Received: by 10.52.96.1 with SMTP id do1mr5368584vdb.285.1301316531313;
        Mon, 28 Mar 2011 05:48:51 -0700 (PDT)
Return-Path: <CSC.CaseStudy@ge.com>
Received: from exprod5og113.obsmtp.com (exprod5og113.obsmtp.com [64.18.0.26])
        by mx.google.com with SMTP id j10si2927556vbl.81.2011.03.28.05.48.49
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 28 Mar 2011 05:48:51 -0700 (PDT)
Received-SPF: neutral (google.com: 64.18.0.26 is neither permitted nor denied 
by best guess record for domain of CSC.CaseStudy@ge.com) client-ip=64.18.0.26;
Authentication-Results: mx.google.com; spf=neutral (google.com: 64.18.0.26 is 
neither permitted nor denied by best guess record for domain of 
CSC.CaseStudy@ge.com) smtp.mail=CSC.CaseStudy@ge.com
Received: from source ([165.156.5.1]) (using TLSv1) by exprod5ob113.postini.com 
([64.18.4.12]) with SMTP
    ID DSNKTZCDsMTZCjACWnouYt+jGk/q2bkjcPsC@postini.com; Mon, 28 Mar 2011 05:48:50 PDT
Received: from unknown (HELO cinmlef06.e2k.ad.ge.com) ([3.159.213.37])
  by Alpmlip06.e2k.ad.ge.com with ESMTP; 28 Mar 2011 08:48:45 -0400
Received: from CINMLVEM20.e2k.ad.ge.com ([3.159.215.51]) by 
cinmlef06.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.4675);
     Mon, 28 Mar 2011 08:47:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Contact Us - Connecticut High School Computer Science Contest
Date: Mon, 28 Mar 2011 08:48:44 -0400
Message-ID: <172F1BF99546404E8F03CFE82510E62908F5802D@CINMLVEM20.e2k.ad.ge.com>
In-Reply-To: <D9A0D0B7EA17564892B2C3A1AB0BB72A0857D097@CINMLVEM20.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Contact Us - Connecticut High School Computer Science Contest
Thread-Index: AcvspsK63tCcY91US2mnLhrW0CtmUQAMy3SgABsaXOA=
References: 
<10306717.8541301247969615.JavaMail.gedotcom@psccispuzon021101v-back> 
<D9A0D0B7EA17564892B2C3A1AB0BB72A0857D097@CINMLVEM20.e2k.ad.ge.com>
From: "~CORP Computer Science Contest Case Study" <CSC.CaseStudy@ge.com>
To: <sreservoir@gmail.com>
Return-Path: CSC.CaseStudy@ge.com
X-OriginalArrivalTime: 28 Mar 2011 12:47:59.0255 (UTC) 
FILETIME=[5E1B9270:01CBED46]

Hi Michael,
    You can submit a multithreaded application.  We will allow the 2 cores =
to be used.

Thanks,

Sean Cady
=A0
T +1 203 944 6807
D * 233 6807

-----Original Message-----
From: ~CORP Computer Science Contest=20
Sent: Sunday, March 27, 2011 7:54 PM
To: sreservoir@gmail.com
Cc: ~CORP Computer Science Contest Case Study
Subject: RE: Contact Us - Connecticut High School Computer Science =
Contest

Hi Michael,

Thank you for your question!  In the future, please email =
CSC.CaseStudy@ge.com (CC'd above) for any case study questions.

I am forwarding this along to them, someone from that team will get back =
to you shortly.

Thanks,
Murali & Kristen

-----Original Message-----
From: @Corp GE Computer Science Contest=20
Sent: Sunday, March 27, 2011 1:46 PM
To: @Corp GE Computer Science Contest
Subject: Contact Us - Connecticut High School Computer Science Contest

Contact Us - 16th Annual Connecticut High School Computer Science =
Contest =20
=20
Subject : Computer Science Contest - Questions or Comments
=20
Name : Michael Zuo
=20
School Name : Amity
=20
Email : sreservoir@gmail.com
=20
Questions/Comments : Seeing as the scoring computer used has two cores, =
would it be permissible to submit a multi-threading program? We assume =
so, based on precedent, but would rather ask just in case.

Original comment by sreservoir on 28 Mar 2011 at 8:10