1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] cheers. ideas.
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20cheers.%20ideas.&In-Reply-To=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"000839.html">
11 <LINK REL=
"Next" HREF=
"000843.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] cheers. ideas.
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20cheers.%20ideas.&In-Reply-To="
17 TITLE=
"[IRCServices] cheers. ideas.">&quot
19 <I>Wed Oct
11 08:
44:
20 PDT
2000</I>
21 <LI>Previous message:
<A HREF=
"000839.html">[IRCServices] cheers. ideas.
23 <LI>Next message:
<A HREF=
"000843.html">[IRCServices] cheers. ideas.
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#840">[ date ]
</a>
27 <a href=
"thread.html#840">[ thread ]
</a>
28 <a href=
"subject.html#840">[ subject ]
</a>
29 <a href=
"author.html#840">[ author ]
</a>
34 <PRE>Services is a READ ONCE, WRITE MANY application. If you make changes to the
35 data in the underlying datastore, be it a database, binary file or text
36 file, the changes would be lost at the next database save.
38 Services would require a lot of work to make it support proper querying of a
39 database. The performance hit services would take would outweigh the benefit
40 imho. If one were to do it properly, with multiple threads loading only the
41 information needed to service the users and channels currently online,
42 things would definately be better. However, let's be honest, this requires a
43 lot of developement, skills and time.
45 What we should focus on is writing an interface for Services that allows
46 external apps to communicate with it.
48 Back to your point about Brasnet,
98MB is a lot. However, it's not totally
49 unreasonable. The thing I'd guess that is really taking a hit is the CPU.
50 The algorithms were never meant to handle so much data. I am definately
51 looking to improve the key ones.
55 ----- Original Message -----
56 From:
"Bruno Lacerda
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">sniffer at sniffer.net
</A>>
57 To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
58 Sent: Wednesday, October
11,
2000 6:
19 PM
59 Subject: Re: [IRCServices] cheers. ideas.
62 ><i> its me again..
64 </I>><i> the data storage, using sql brings a lot of new possibilitys, with real
65 </I>><i> databases
3rd party programs/sites may use and change the information,
67 ><i> is really interesting, develop internet portals based on the
69 ><i> information, search for users with html forms, retrieve/change password..
70 </I>><i> integration is the main ideia.
72 </I>><i> im currently helping a irc network called BrasNet (Brazil), the nick.db
74 ><i> nothing more than
98 MB.. this _really_ stress the box.. with an indexed
75 </I>><i> database the searches and querys about nicks and chans registrations and
76 </I>><i> passwords authentication would be much more reliable!
78 </I>><i> well.. post you comment..
80 </I>><i> who is the services coding leader? Hi mr coder! (exchange ideas..)
84 </I>><i> Bruno Lacerda
85 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">sniffer at sniffer.net
</A>
86 </I>><i> <A HREF=
"http://sniffer.net">http://sniffer.net
</A>
88 </I>><i> ----- Original Message -----
89 </I>><i> From:
"Chris Wiest
" <<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">kwahraw at relic.net
</A>>
90 </I>><i> To:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
91 </I>><i> Cc:
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org
</A>>
92 </I>><i> Sent: Wednesday, October
11,
2000 10:
09 AM
93 </I>><i> Subject: Re: [IRCServices] cheers. ideas.
96 </I>><i> > *shrug* perspectives and experience I suppose come into play here. While
97 </I>><i> > it may be the o/s we are operating from, which is FreeBSD4.0 (I am
98 </I>><i> > hesitant to move to
4.1, though the CD's are sitting on my desk at
99 </I>><i> > work due to its relative newness, and some network issues I've had with
100 </I>><i> > it on our development machine at work),
4.0 one would think would be
102 ><i> > to keep mysql up and running. The issue seems to come about with
104 ><i> > query requests and attempts to place entries into the database
105 </I>><i> > simultaneously. Again, my point is an XML format would perhaps be the
106 </I>><i> > better way to go, as it is not dependent on a
3rd party application
107 </I>><i> > working properly. Even if you have not had issues with the application
108 </I>><i> > itself, there is still the exposure that a third party application (your
109 </I>><i> > sql program) could crash, which on a philosophical level (putting aside
111 ><i> > above mentioned personal problems with the application) is a bad way to
112 </I>><i> > go. I am not saying not to go ahead with sql, I am just pointing out a
113 </I>><i> > pretty clear downfall to doing so.
115 </I>><i> > --CDW
117 </I>><i> > On Wed,
11 Oct
2000, Scott Seufert wrote:
119 </I>><i> > > At
07:
33 AM
10/
11/
2000 -
0400, you wrote:
120 </I>><i> > > >i debated, and even played with storing/retreiving to mysql. The
122 </I>><i> > > >that I've found is that you then deal with ensuring the sql program
125 </I>><i> > > >and running, and sql tends to crash (we actually have a sql based
127 </I>><i> > > >currently that has an average uptime of
2 to
3 days). I don't know
129 ><i> > > >anyone else has experienced this, however it seems to kinda be
130 </I>><i> > > >standard. We deal with
1600 to
2000 users simultaneous, they tend to
132 </I>><i> > > >pissy when our services go boom, and rightly so. I'm not saying not
134 ><i> > > >move to sql (though I'd say xml seems a better option), but I am
136 ><i> > > >that given sql's uptime, it can be an issue.
137 </I>><i> > > >
138 </I>><i> > > >--CDW
139 </I>><i> > >
140 </I>><i> > > <snip
>
141 </I>><i> > >
142 </I>><i> > > In my experience I have seen quite the opposite, SQL tends to be quite
143 </I>><i> > > stable. Offering reliable support for tens of thousands. This
145 ><i> > > includes mySQL and MS SQL.
146 </I>><i> > >
147 </I>><i> > > Scott Seufert
148 </I>><i> > > aka katsklaw
149 </I>><i> > > Server Admin
150 </I>><i> > > Excalibre.ShadowFire.Org
151 </I>><i> > >
152 </I>><i> > >
153 </I>><i> > > ---------------------------------------------------------------
154 </I>><i> > > To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
155 </I>><i> > > with
"unsubscribe ircservices
" in the body, without the quotes.
156 </I>><i> > >
159 </I>><i> > ---------------------------------------------------------------
160 </I>><i> > To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
161 </I>><i> > with
"unsubscribe ircservices
" in the body, without the quotes.
165 </I>><i> ---------------------------------------------------------------
166 </I>><i> To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
167 </I>><i> with
"unsubscribe ircservices
" in the body, without the quotes.
171 ---------------------------------------------------------------
172 To unsubscribe, send email to
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org
</A>
173 with
"unsubscribe ircservices
" in the body, without the quotes.
182 <LI>Previous message:
<A HREF=
"000839.html">[IRCServices] cheers. ideas.
184 <LI>Next message:
<A HREF=
"000843.html">[IRCServices] cheers. ideas.
186 <LI> <B>Messages sorted by:
</B>
187 <a href=
"date.html#840">[ date ]
</a>
188 <a href=
"thread.html#840">[ thread ]
</a>
189 <a href=
"subject.html#840">[ subject ]
</a>
190 <a href=
"author.html#840">[ author ]
</a>
projects / irc.git / blob