[Zope] Refresh Products without restart
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm starting to port some of our Products form Zope2.11 to Zope2.13. Why is the Refresh Tab gone form the Product Object. A quick look in the Source revealed that the refresh tab is still there only the manage_refresh method is gone. Is there another way to refresh single Products without restarting the whole server. Regards Estartu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQCVAwUBUonD+wzx22nOTJQRAQKNfgQAjgCWRnfgu5N4N3RovNucOMOHVrfGeKLM tPTDlxZWPnIBIpUN82XBOKM28p5Sg8rCDgPspfNbCbG8MqNFmeaH+KwwIohlS/X4 35nHo+XEi5vrJnBNO9jX5gXp8EwQ575HUD8KYKsNCyXgSLS0K1YKx084C0JjXCPJ sZcZcfx5AHk= =Kfj9 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Request time grows with memory size
HI,
I've encounters a performance Problem with Zope. Some requests take very
long time to process while others are served very fast. All request go for
the URL. The time for the delayed Requests grows with the memory size of
the Zope Process. It's direct proportional.
I have generated a chart showing the request times and memory size of the
Zope Process. The chart can be found at http://etustar.ze.tum.de/frontend.jpg
Our watchdog system restarts the Zope Process when it reaches 7.3 Gig
Memory. The physical memory of the server is 16 Gig and its only used for
the zope Server. There are at least 7 Gig Memory free.
As you can see most of the requests are delivered within 2 seconds but some
take up to 12 seconds. The Requests monitored are the request of our
watchdog system. These requests are send approximately every 20 sec.
When I set the restart memory limit higher the request time of the delayed
request continues to grows proportionally.
This server is part of a pool of 19 Servers. All are connected to one ZEO
server. All show the same effect.
We observe the same effect with regular requests. Some are served at normal
speed but some requests are delayed.
Any idea what causes this effect and how to fix it.
Greetings
Gerhard Schmidt
--
-----
Gerhard Schmidt | E-Mail: schm...@ze.tum.de
TU-München|
WWW & Online Services |
Tel: 089/289-25270|
Fax: 089/289-25257| PGP-Publickey auf Anfrage
signature.asc
Description: OpenPGP digital signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] You are not allowed to access 'a particular str' in this context
Dieter Maurer schrieb:
> Gerhard Schmidt wrote at 2008-1-24 16:56 +0100:
>> I have a rather strange Problem.
>>
>> I have a PersistentList containing PersistentMapping objects.
>>
>> [{'Status': 'Read', 'Confirm': False, 'Read': DateTime('2008/01/24
>> 16:03:32.508 GMT+1'), 'Expires': None, 'SenderID': 'DC83D1F1DB88CDE8',
>> 'Date':
>> DateTime('2008/01/24 15:51:50.998 GMT+1'), 'Message': 'Da ist ein permission
>> test', 'ID': '[EMAIL PROTECTED]'}]
>>
>> When do a tal:repeat="message here/getMessages" and a tal:replace="message"
>> everything functions as expected. When i try tal:replace="message/ID" I get
>> an
>> Unauthorized Exception "You are not allowed to access 'a particular str' in
>> this context"
>
> Reconfigure your "error_log" object to not ignore "Unauthorized" exceptions,
> reproduce the error and then look at the corresponding traceback.
>
> I expect that the "message" object implements a "__bobo_traverse__"
> method (or gets one through "Five").
> Zope is a bit stupid when "__bobo_traverse__" returns an object
> without security declarations -- such as e.g. a string.
> In this case, it insists that "getattr" must return the same object
> and raise "Unauthorized" otherwise.
Time2008/01/25 12:01:53.125 GMT+1
User Name (User Id) DC83D1F1DB88CDE8 (DC83D1F1DB88CDE8)
Request URL http://devportal:6080/portal_communications/manage_messagequeue
Exception Type Unauthorized
Exception Value You are not allowed to access 'a particular str' in
this context
Traceback (innermost last):
Module ZPublisher.Publish, line 115, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 41, in call_object
Module Shared.DC.Scripts.Bindings, line 311, in __call__
Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 113, in _exec
Module Products.PageTemplates.PageTemplate, line 104, in pt_render
-
Module TAL.TALInterpreter, line 238, in __call__
Module TAL.TALInterpreter, line 281, in interpret
Module TAL.TALInterpreter, line 715, in do_condition
Module TAL.TALInterpreter, line 281, in interpret
Module TAL.TALInterpreter, line 691, in do_loop_tal
Module TAL.TALInterpreter, line 281, in interpret
Module TAL.TALInterpreter, line 455, in do_optTag_tal
Module TAL.TALInterpreter, line 437, in no_tag
Module TAL.TALInterpreter, line 281, in interpret
Module TAL.TALInterpreter, line 531, in do_insertText_tal
Module Products.PageTemplates.TALES, line 227, in evaluateText
Module Products.PageTemplates.TALES, line 221, in evaluate
- URL: manage_messagequeue
- Line 17, Column 9
- Expression: standard:'message/ID'
- Names:
{'container': ,
'context': ,
'default': ,
'here': ,
'loop': ,
'modules':
,
'nothing': None,
'options': {'args': ()},
'repeat': ,
'request': http://devportal:6080/portal_communications/manage_messagequeue>,
'root': ,
'template': ,
'traverse_subpath': [],
'user': }
Module Products.PageTemplates.Expressions, line 185, in __call__
Module Products.PageTemplates.Expressions, line 173, in _eval
Module Products.PageTemplates.Expressions, line 127, in _eval
- __traceback_info__: message
Module Products.PageTemplates.Expressions, line 338, in restrictedTraverse
- __traceback_info__: {'path': ['ID'], 'TraversalRequestNameStack': []}
Unauthorized: You are not allowed to access 'a particular str' in this
context
Regards
Gerhard
--
-
Gerhard Schmidt | E-Mail: [EMAIL PROTECTED]
TU-München|
WWW & Online Services |
Tel: 089/289-25270|
Fax: 089/289-25257| PGP-Publickey auf Anfrage
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] You are not allowed to access 'a particular str' in this context
Martijn Jacobs schrieb: > Does this problem only occure with message/ID ? Or also with > message/Message or message/SenderId ? The problem is on all Strings. DateTime Objects working. > Which version of zope are you using? Zope 2.9.7-final, python 2.4.4, freebsd7 Gerhard -- ----- Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW & Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey on Request ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] You are not allowed to access 'a particular str' in this context
Hi all,
I have a rather strange Problem.
I have a PersistentList containing PersistentMapping objects.
[{'Status': 'Read', 'Confirm': False, 'Read': DateTime('2008/01/24
16:03:32.508 GMT+1'), 'Expires': None, 'SenderID': 'DC83D1F1DB88CDE8', 'Date':
DateTime('2008/01/24 15:51:50.998 GMT+1'), 'Message': 'Da ist ein permission
test', 'ID': '[EMAIL PROTECTED]'}]
When do a tal:repeat="message here/getMessages" and a tal:replace="message"
everything functions as expected. When i try tal:replace="message/ID" I get an
Unauthorized Exception "You are not allowed to access 'a particular str' in
this context"
I can access all DateTime objects. Only the strings a not allowed.
There is no difference when getMessages return of the Original list and when I
build a new list with copies of the PersistentMapping objects.
To get this working I have to create new Dictionary from the Persistent
Mappings add them to an normal List and return this list.
ret = []
for test in self.msglist :
temptest = {}
for (key,value) in test.items() :
temptest[key] = value
ret.append(temptest)
return ret
That's a real performance killer as the list is read quite frequently.
Any Idea how to fix this.
Gerhard
--
-
Gerhard Schmidt | E-Mail: [EMAIL PROTECTED]
TU-München|
WWW & Online Services |
Tel: 089/289-25270|
Fax: 089/289-25257| PGP-Publickey on request
signature.asc
Description: OpenPGP digital signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Scaling problems, or something else?
On Wed, May 16, 2007 at 05:52:16PM -0400, Paul Winkler wrote:
> On Wed, May 16, 2007 at 04:24:56PM -0500, Jens Vagelpohl wrote:
> > There's a difference between scaling and making something faster. ZEO
> > makes a single instance slower, right. But you can deal with more
> > requests concurrently using ZEO. That's what I consider "scaling".
>
> Agreed. But at the same time, I don't think it makes sense to keep
> deploying more and more badly tuned instances. That's what I consider
> "blind shotgun scaling" :) You need to scale, but you also need to
> tune - and you need to be pragmatic about which is the appropriate
> approach at any given point in time.
I would love to tune our system, but not using ZEO isn't an option. I don't
see how a single Server ever will be able to do what 13 Server do right now.
Our system is a single Instance. With up to 70k requests per hour (20
requests per second). I don't see a way to get rid of the ZEO server.
We have expirienced some problem with ZEO when requests take to long.
Sometimes we have Problems like this
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.29:52569)
Transaction blocked waiting for storage. Clients waiting: 1.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.36:56041)
Transaction blocked waiting for storage. Clients waiting: 2.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.33:63884)
Transaction blocked waiting for storage. Clients waiting: 3.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.34:64355)
Transaction blocked waiting for storage. Clients waiting: 4.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.25:63215)
Transaction blocked waiting for storage. Clients waiting: 5.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.28:58213)
Transaction blocked waiting for storage. Clients waiting: 6.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.30:59149)
Transaction blocked waiting for storage. Clients waiting: 7.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.31:58930)
Transaction blocked waiting for storage. Clients waiting: 8.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.35:64097)
Transaction blocked waiting for storage. Clients waiting: 9.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.27:63627)
Transaction blocked waiting for storage. Clients waiting: 10.
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.26:63146) Blocked
transaction restarted. Clients waiting: 9
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.29:52569) Blocked
transaction restarted. Clients waiting: 8
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.36:56041) Blocked
transaction restarted. Clients waiting: 7
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.33:63884) Blocked
transaction restarted. Clients waiting: 6
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.34:64355) Blocked
transaction restarted. Clients waiting: 5
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.25:63215) Blocked
transaction restarted. Clients waiting: 4
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.28:58213) Blocked
transaction restarted. Clients waiting: 3
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.30:59149) Blocked
transaction restarted. Clients waiting: 2
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.31:58930) Blocked
transaction restarted. Clients waiting: 1
--
2007-05-21T03:36:22 INFO ZEO.StorageServer (56016/10.152.64.35:64097) Blocked
transaction restarted.
This incident wasn't a Problem because it was resolved within on second.
But sometimes situations like this take up tum 30 seconds to resolve.
The site is completly unresponsiv in this time and take up to 10 minutes
to resume normal opration (Responsetimes < 1 sec per dynamic page)
I haven't been able to track down the Problem that causes this. But the
frequency has droped quite dramatic since we updated our fontend Servers
to more recent CPUs.
It seams there is a posibility for an deadlock when requests take to much
time to process.
But the main Problem what we have is the memory growth of the Zope server
processes. They grow to 500 MB of Memory bevor serving the first request.
an wile running the constantly growing until the hit the limit of the
physical memory. When they do, they slow down very dramaticaly
(responstimes 800% higher than usual) we have done some debugging and it
seams that die python garbage collection kicks in and kills the whole
performance. The only solution we have com up with is to restart the zope
Server before the hit the physical memory limit.
Bye
Estartu
--
Re: [Zope] Scaling problems, or something else?
On Thu, May 10, 2007 at 02:10:40AM +0200, Gaute Amundsen wrote: > So there is no other possible limit in a zope instance than IO or CPU? > If cpu was the limiting factor I would see the 2 python processes running 90% > and dozens of httpd's taking up the rest? I'm running a zope site with up 70k requests per hour (40k on avarage). I've noticed that the main reason vor performance problem is not enough memory. We are running 13 Frontend Zope servers and a ZEO Backend. All our frontendservers have 8gig ram. Zope gets major performance Problems when it reaches the limit of physical memory. Check your system if the. So having 2 zope Processes on the same system increases the Problem. Zope 2.7 doesn't scale very well with the ZEO. The more Frontend server you get the more Read Conflicts you have. Migration to Zope2.8 reduced this problem. I have build a squid proxy in reverse mode take the Request and spead them per round robin to the ZopeFrontends. This takes quite a lot load from the systems as the squid caches most of the static content (images, PDF files etc). Regard Estartu -- -------- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpyU9o8lG1cL.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] zeoctl logreopen doesn't work
Hi, since i'm running my zeo.log at debug level in grows quite large. I've tried to rotate the log daily by renaming the zeo.log and call zeoctl logreopen. ./bin/zeoctl logreopen kill(6319, 31) signal 31 sent to process 6319 But no new zeo.log is created and all log entries still go to the old file. How can I get zeo to create a new logfile without restarting the zeo server completely. Bye Estartu -------- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] ZEO Problem Clients Waiting
On Mon, Aug 07, 2006 at 09:09:56PM +0200, Dieter Maurer wrote:
> Gerhard Schmidt wrote at 2006-8-7 15:54 +0200:
> > ...
> >2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518)
> >Transaction
> >+blocked waiting for storage. Clients waiting: 1.
> > ...
> >2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463)
> >Blocked transaction restarted. Clients waiting: 1
> >2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.23:52518)
> >Blocked transaction restarted.
> >
> >This one was a very quick one only 30 seconds. I have Blocked Transaktion
> >that ware waiting for more than 2 minutes.
>
> This means that you have very long transactions -- transactions that
> take very long to commit.
>
> ZEO cannot commit two transactions for the same storage at the same time.
> Therefore, it sets a storage look when a transaction commit begins for
> the storage.
>
> If another transaction tries to commit to the same storage, the transaction
> is blocked until the first transaction commit completes.
> That's your "Transaction blocked waiting for storage"
>
> When the commit is completed, then a waiting transaction is restarted.
> That's your "Blocked transaction restarted".
>
> You should try to understand where the huge transactions come from.
> Very often, they are caused by poor persistency design (either far
> too huge objects or an immense number of tine objects or just some stupidity
> (e.g. writing objects unnecessary).
I have benchmarked my Harddisk (which is at the moment an emergency system
because of a hardware failure of the main system) it has 40 MB/sec write
speed and it doesn't show high io load when we have such a hangup. I have
tried to create an object with 50 MB in the storage the ZEO server had no
problem with that. calculating this, there has to be an objekt of CD Image size
to cause the write to take more then 30 sec. But this whould
mean that the Data.fs whould grow at least a 2-3 Gig a Day (we have 5-6
such hangups a day) but it only grows arround 50-100 MB a per Day
(difference befor and after Pack) and real growth is 2-10 MB per Day.
To the number of tiny objects. I have the zeo.log on debug level. Entries
like these seam to be the objekts that are requested to be written.
2006-08-08T07:44:12 DEBUG ZEO.zrpc.Connection(S) (10.152.64.21:50210) calling
storea('\x00\x00\x00\x00\x0057\x85', '\x03gZW\x00\xa0\xa1\xcc', '(...
I don't see a lot of them bevor a hangup occur.
So there are two areas where the Problem could be located. The filesystem
of the host system and in the network between the App-Server and the Zeo.
To understand this can you tell me when a transaction is started and when
its closed. Does the Zeo server wait until all data is recieved bevor the
transaction is started or does the transaktion start when the datatransfer
from the appserver starts.
Bye
Estartu
Gerhard Schmidt| Nick : estartu IRC : Estartu |
Fischbachweg 3 || PGP Public Key
86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request
Germany||
pgpRboq3a8VZt.pgp
Description: PGP signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] ZEO Problem Clients Waiting
HI, we have quite a Problem with out Zope/Zeo system. We run at the moment Zope cluster with 10 application servers and a zeo server with Filestorage. Our Data.fs is 3.5 Gig at the moment (after Pack). I runs most of the time without problem. But sometimes things screw up 2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction +blocked waiting for storage. Clients waiting: 1. 2006-08-07T14:29:29 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Transaction +blocked waiting for storage. Clients waiting: 2. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Transaction +blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Transaction +blocked waiting for storage. Clients waiting: 4. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Transaction +blocked waiting for storage. Clients waiting: 5. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Transaction blocked waiting for storage. Clients waiting: 6. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Transaction blocked waiting for storage. Clients waiting: 7. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Transaction blocked waiting for storage. Clients waiting: 9. 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Blocked transaction restarted. Clients waiting: 8 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Blocked transaction restarted. Clients waiting: 6 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Blocked transaction restarted. Clients waiting: 5 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Blocked transaction restarted. Clients waiting: 4 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Blocked transaction restarted. Clients waiting: 3 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Transaction blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:49 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Blocked transaction restarted. Clients waiting: 1 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. This one was a very quick one only 30 seconds. I have Blocked Transaktion that ware waiting for more than 2 minutes. When there a 9 Clients waiting our complete Zopesite comes to a halt until the transaction is restarted. As im not realy deep in the ZODB/ZEO subject. Can anybody pinpoint me where to look for the Problem. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpngdBFhioow.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zeo as a Zeo Client
On Wed, May 03, 2006 at 09:19:31AM +0200, Andreas Jung wrote: > > > --On 3. Mai 2006 09:15:45 +0200 Gerhard Schmidt <[EMAIL PROTECTED]> wrote: > > > >Every major innovation was extremely uncommon bevor it was implemented. > >So thats not a reason not to do it. Is there a way to get this to work. > >I Think it whould be a very nice feature. Because it whould increase the > >scalability. When we can bring the cache to work it will improve > >perfomance for large sites as well. > > There are lot of things that would be nice if they were implemented.. > The best chance to get this feature into Zope is either to implement it > yourself or by funding the development. If I had the Time I whould do it. My ToDo List goes around up to the moon an back twice. About the funding I have to talk to my superior when he is back from his vacation. Bye Estartu ------------ Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] | auf Anfrage/ Tel: 08232 77 36 4 | Dienst: [EMAIL PROTECTED] |on request Fax: 08232 77 36 3 || ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zeo as a Zeo Client
On Wed, May 03, 2006 at 08:56:28AM +0200, Andreas Jung wrote: > > > --On 3. Mai 2006 08:35:48 +0200 Gerhard Schmidt <[EMAIL PROTECTED]> wrote: > > > > > >It was lost in the 2.6 version of the Zope book i have scanned the Page > >with the Picture. See http://etustar.ze.tum.de/zopebook.jpg > > > > Scary...no idea why it is in the printed edition...at least the 2.6 and 2.7 > edition does not show such a setup. As mention earlier such a setup is not > supported and not supposed to work. *At least* it is *extremely* uncommon. Every major innovation was extremely uncommon bevor it was implemented. So thats not a reason not to do it. Is there a way to get this to work. I Think it whould be a very nice feature. Because it whould increase the scalability. When we can bring the cache to work it will improve perfomance for large sites as well. Bye Estartu -------- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zeo as a Zeo Client
On Wed, May 03, 2006 at 08:22:22AM +0200, Andreas Jung wrote: > > > --On 3. Mai 2006 08:11:44 +0200 Gerhard Schmidt <[EMAIL PROTECTED]> wrote: > > > >The question is why is it impossible to run a zeo as a zeoclient. > > Because this usecase was/is never supported. > > >I can > >setup a zeo with a zeoclient storage i See teh invalidations coming from > >the backend zeo. So this part works. The part with the client connect > >works also. Just the connect between both is missing. And as i said > >such a config is descibed in the Zope Book 2.5 version on page 230. > > We don't have a paper copy at hand. I can not find any description of your > usecase in the 2.7 edition of the Zope Book...please verify it. It was lost in the 2.6 version of the Zope book i have scanned the Page with the Picture. See http://etustar.ze.tum.de/zopebook.jpg Bye Estartu ---- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zeo as a Zeo Client
On Tue, May 02, 2006 at 10:24:29PM +0200, Dieter Maurer wrote: > Gerhard Schmidt wrote at 2006-5-2 09:52 +0200: > > ... > >I try to reduce the load of the line between the backup Computing Center > >and the Mainsite by having a zeo server as Proxy between the zope server > >at the backup site an the ZEO at the main site. > > You will gain nothing -- as ZEO does not implement a cache > but forwards any request immediately to the storage. > Its only task is to synchronize concurrent access to a single > storage -- nothing else. For my primary goal this whould do perfectly. Primarily I whan't the zeo at backup site just to foward the request to the main site. All I want is the i have only one place to change the config in case of a failure at the main site. Nothing more. Everything else whould be nice to have. But still the even just forwarding does not work right now. Bye Estartu ------------ Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zeo as a Zeo Client
On Tue, May 02, 2006 at 10:23:40AM -0400, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Gerhard Schmidt wrote: > > > I try to reduce the load of the line between the backup Computing Center > > and the Mainsite by having a zeo server as Proxy between the zope server > > at the backup site an the ZEO at the main site. > > > > Secound part is that the zeo at the backupsite can easily reconfigured in > > a normal ZEO when the mainsite is offline. So I don't have to reconfigure > > all zeoclients at the backupsite. The Data.fs is copied every hour to the > > backup site so that a have an up to one our backup of the data.fs in case > > of a desaster at the main site. > > > > A configuration like that is described in the Zope Book on page 230. > > > > Besides I have found that with a growing number of zeo clients the Zeo > > server gets slower but neither the CPU nor the Harddisk IO is at the limit. > > We have a load of 0.2 to 0.3 and disk IO arrond 2-3 MB/sec. We have 12 > > zeoclients at the moment and 12 more are planed for the backup site. > > I would look for a replication strategy to create your "intermediate" > storage server: the setup you are trying is not supported by the > current ZEO setup. Such strategies include: > > - Zope Corp's "Zope Replication Services" product, which keeps the > "secondary" storage servers synchronized with the primary via > the "spread" toolkit. > > - DirectoryStorage can be used to do replication via rsync. > > - Another possibility would be to use 'repozo' to create deltas > on the primary, and then propagate them to the secondary via > rsync, then apply them via 'repozo'. I have never said that I want to have an realtime replaication. All I want is a ZEO at the backup site that forwards the request to the main site. Thats to provide a single point where i have to change the configuartion when a desaster at the main site happens. I simply don't want to change the configuration of all zope server at the backup site which are 12 at the first step an will grow as needed. As I said. The is a notable drop in perfomance with growing number auf connected clients. even if the clients aren't fetching objekts. I think this is becaus auf the growing invalidation overhead. We have a site with many write requests. So I hoped when i have a second zeo that the performance loss can be reduced. That's the second reason for the for this setup. As i figured that the cache is implemented in the zeoclient not in the zope server itself i thought ist might get me some proxy capabilities. But thats whould have been the sugar on the Top nothing realy needed as we have a 1 GBit connect between main and backup site. The question is why is it impossible to run a zeo as a zeoclient. I can setup a zeo with a zeoclient storage i See teh invalidations coming from the backend zeo. So this part works. The part with the client connect works also. Just the connect between both is missing. And as i said such a config is descibed in the Zope Book 2.5 version on page 230. Why has the support for such configurations droped in newer versions. We are planing to purchase ZRS later this year to setup an automatic failover. But as mentioned here. We can't use the ZRS backup servers when running in normal mode becaus they are read only. So I need an setup wer I can run a normal zeo in zeoclient mode when the mainsite is online. This zeo will be shutdown and replaced by the ZRS backup when the mainsite goes down. Otherwise i have to mess with IP takeover and other very messy strategies. I'm trying to get this as simple and as stable as possible. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zeo as a Zeo Client
On Tue, May 02, 2006 at 08:51:12AM +0200, Andreas Jung wrote: > > > --On 2. Mai 2006 08:31:17 +0200 Gerhard Schmidt <[EMAIL PROTECTED]> wrote: > > >Hallo, > > > >I am trying to install a setup like shown below > > > >ZEO_M > > | -- ZEO_B > > | | -- ZOPE > > | | -- ZOPE > > | | -- ZOPE > > | ... > > | -- ZOPE > > | -- ZOPE > > ... > > > > You are trying to create a cascade of multiple ZEO Clients? That looks > very odd. Usually a ZEO client talks directly to a ZEO server. I try to reduce the load of the line between the backup Computing Center and the Mainsite by having a zeo server as Proxy between the zope server at the backup site an the ZEO at the main site. Secound part is that the zeo at the backupsite can easily reconfigured in a normal ZEO when the mainsite is offline. So I don't have to reconfigure all zeoclients at the backupsite. The Data.fs is copied every hour to the backup site so that a have an up to one our backup of the data.fs in case of a desaster at the main site. A configuration like that is described in the Zope Book on page 230. Besides I have found that with a growing number of zeo clients the Zeo server gets slower but neither the CPU nor the Harddisk IO is at the limit. We have a load of 0.2 to 0.3 and disk IO arrond 2-3 MB/sec. We have 12 zeoclients at the moment and 12 more are planed for the backup site. Regards Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zeo as a Zeo Client
in call r_flags, r_args = self.wait(msgid) File "/usr/local/www/Zope28/lib/python/ZEO/zrpc/connection.py", line 638, in wait asyncore.poll(delay, self._singleton) File "/usr/local/lib/python2.4/asyncore.py", line 122, in poll r, w, e = select.select(r, w, e, timeout) KeyboardInterrupt I started it with runzope and killed it with CRTL-c. I had it once waiting for 2 hours without any difference. here is the ZEO_B config file # ZEO configuration file %define INSTANCE /data/zope/zeoproxy01 address 8110 read-only false invalidation-queue-size 100 # pid-filename $INSTANCE/var/ZEO.pid # monitor-address PORT # transaction-timeout SECONDS server 10.152.64.1:8100 storage main name main # var $INSTANCE/var # client zeoproxy01 # cache-size 600MB level debug path $INSTANCE/log/zeo.log program $INSTANCE/bin/runzeo socket-name $INSTANCE/etc/zeo.zdsock daemon true forever false backoff-limit 10 exit-codes 0, 2 directory $INSTANCE default-to-interactive true # user zope python /usr/local/bin/python zdrun /usr/local/www/Zope28/lib/python/zdaemon/zdrun.py # This logfile should match the one in the zeo.conf file. # It is used by zdctl's logtail command, zdrun/zdctl doesn't write it. logfile $INSTANCE/log/zeo.log The Zope Server directly on ZEO_M works without problems. Regards Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] unpickle error on Data.fs pack
On Wed, Jan 25, 2006 at 12:52:10PM +0100, Gerhard Schmidt wrote: > I've tried to recover the data.fs with fsrecover but it returns > without error and the error remains. fsrefs.py terminates with > an error. Any idea how to fix the Data.fs. fsrefs.py returns the following. Traceback (most recent call last): File "/usr/local/www/Zope/bin/fsrefs.py", line 189, in ? main(path) File "/usr/local/www/Zope/bin/fsrefs.py", line 161, in main refs = get_refs(data) File "/usr/local/www/Zope/bin/fsrefs.py", line 105, in get_refs u.noload() # instance state info cPickle.UnpicklingError: invalid load key, ''. Thats all. The Data.fs is about 3Gig. Bye Estartu --------- Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW & Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage pgphjjYxUYG04.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] unpickle error on Data.fs pack
Hi,
since three days we have problems when packing the Data.fs.
2006-01-25T03:40:42 ERROR(200) zrpc:7266 Error raised in delayed method
Traceback (most recent call last):
File "/usr/local/www/Zope/lib/python/ZEO/StorageServer.py", line 991, in run
result = self._method(*self._args)
File "/usr/local/www/Zope/lib/python/ZEO/StorageServer.py", line 315, in
_pack_impl
self.storage.pack(time, referencesf)
File "/usr/local/www/Zope/lib/python/ZODB/FileStorage.py", line 1582, in pack
opos = p.pack()
File "/usr/local/www/Zope/lib/python/ZODB/fspack.py", line 700, in pack
self.gc.findReachable()
File "/usr/local/www/Zope/lib/python/ZODB/fspack.py", line 456, in
findReachable
self.findReachableAtPacktime([z64])
File "/usr/local/www/Zope/lib/python/ZODB/fspack.py", line 531, in
findReachableAtP
acktime
todo.extend(self.findrefs(pos))
File "/usr/local/www/Zope/lib/python/ZODB/fspack.py", line 604, in findrefs
return referencesf(self._file.read(dh.plen))
File "/usr/local/www/Zope/lib/python/ZODB/referencesf.py", line 38, in
referencesf
raise ValueError, 'Error unpickling %r' % p
ValueError: Error unpickling
'((U\x0eBTrees.OIBTreeq\x01U\x08OIBucketq\x02tq\x03Nt.((
U\x05nchenq\x04J\xc6{a\xfeU\x0fnchen/ottobrunnq\x05J\xbd\xeby\xcfU\x04ndigq\x06J\n\xf
0}QU\x05ndnisq\x07J\xd9\xdc\xbfIU\x02neq\x08J1!\x15\xe9U\x05nebenq\tJT]4\xc0U\x03netq
\nJ\xf3cU\xb6U\x04net/q\x0bJ\nM\xe5\xd6U\x07networkq\x0cJ\xf5\x85!\xe5U\tnetzartigq\r
J\xd4\xf9\x906U\x03neuq\x0eJv\xd7>\xe9U\x04neueq\x0fJW\xedD\xd8U\x05neuenq\x10J0>!\x0
7U\x05neuesq\x11J\xb9\xa5\xb4sU\x08neuestenq\x12JW2\xcc-U\x07nftigenq\x13J\xd5"i>U\x0
3ngeq\x14J%\xa9X\x10U\x06ngerenq\x15J>\x1d\x14YU\x04ngigq\x16J\xc4\xe6\xe5\xd4U\x06ng
igenq\x17J}\xbd\xffpU\nngigkeitenq\x18J)]\x06IU\x05nichtq\x19J\x0bgy>U\x07nkungenq\x1
aJC4\xf7\x10U\x04nnenq\x1bJU\xc4bFU\x04nochq\x1cJ\xb4\xf6\xcdUU\x07norbertq\x1dJ-\xf3
\xd7\x8fU\x06normenq\x1eJ[\x84\xd4\xaeU\x07normungq\x1fJ\xf4\xe9\xfc\xfcU\x08notebook
q
J\xf7\xf2\x9e\xf9U\x0fnotebookeinsatzq!J`\x8fRiU\tnotebooksq"J\xba>\xecvU\x12notebo
okverwendungq#J_R\x10\x9aU\x02nrq$J\xfcSg\xddU\x05nscheq%J-\x88\xf8\xccU\x06nstigeq&J
\xa35\x0e\xcdU\x04nterq\'J\xb1\x94\x9b\xeeU\nnumerischeq(Jf\\n\xfeQ\x03nurq)J\xd2\x95
C\xf4U\x0cnutzbringendq*J\xd3\x84\x84\xeaU\x06nutzenq+J\xa7^\x86IU\tnutzungsmq,J\xc1\
xca\xb9LU\x02obq-J\xbe\xb7e\x94U\x06objectq.J\xaaP\x14\xf9U\x04oderq/J\\0\xc2(U\x05od
imaq0J\xcd\xf9\x0f:t(U\x08\x00\x00\x00\x00\x00%\xa5\xdaq1(U\x0eBTrees.OIBTreeq2U\x08O
IBucketq3ttq4Qtq5.'
--
I've tried to recover the data.fs with fsrecover but it returns
without error and the error remains. fsrefs.py terminates with
an error. Any idea how to fix the Data.fs.
The System is still up an running and no error shown so far.
Bye
Estartu
Gerhard Schmidt| Nick : estartu IRC : Estartu |
Fischbachweg 3 || PGP Public Key
86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request
Germany||
pgpCXh1QIuAmp.pgp
Description: PGP signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] repozo problem
Hi, I have some problems with repozo. I have setup repozo for backup of our Data.fs about two years ago and it worked without problem until 4 weeks ago. Since than it behaves very strange. I am running repozo with den follwing parameters. /usr/local/bin/python /usr/local/www/Zope/bin/repozo.py -v -z -B -f /data/zope/zeo/var/Data.fs -r /data/share/backup/data.fs/ and I get the following error. looking for files between last full backup and 2006-01-23-03-43-40... files needed to recover state as of 2006-01-23-03-43-40: /data/share/backup/data.fs/2006-01-22-03-44-01.fsz Traceback (most recent call last): File "/usr/local/www/Zope/bin/repozo.py", line 501, in ? main() File "/usr/local/www/Zope/bin/repozo.py", line 494, in main do_backup(options) File "/usr/local/www/Zope/bin/repozo.py", line 431, in do_backup reposz, reposum = concat(repofiles) File "/usr/local/www/Zope/bin/repozo.py", line 248, in concat bytesread += dofile(func, ifp) File "/usr/local/www/Zope/bin/repozo.py", line 192, in dofile data = fp.read(todo) File "/usr/local/lib/python2.3/gzip.py", line 224, in read self._read(readsize) File "/usr/local/lib/python2.3/gzip.py", line 289, in _read self._read_eof() File "/usr/local/lib/python2.3/gzip.py", line 308, in _read_eof raise IOError, "CRC check failed" IOError: CRC check failed when I run it without compression the backup works but it doesn't do incremental. reprozo is run by cron ever 2 hours and the Data.fs is packed only once a day. Repozo reports looking for files b/w last full backup and 2006-01-10-11-47-49... files needed to recover state as of 2006-01-10-11-47-49: /data/share/backup/data.fs/2006-01-10-09-47-27.fs repository state: 3283188277 bytes, md5: 1ea3199aa1f6be3dafccc5d63ed7f4a1 current state : 3337668930 bytes, md5: 57a964c569e06f6125eda24c74aab079 backed up state : 3283188277 bytes, md5: 17f9b380d5b1ad33deb99942a20545f5 file changed, possibly because of a pack (full backup) writing full backup: 3339094688 bytes to /data/share/backup/data.fs/2006-01-10-11-56-03.fs everytime it's started. I have suspected an inconsitency in the Data.fs but i've done a fsrecover twice since the problems started and it came out without errors. The Zope systems and the daily pack are working without Problems. Our Data.fs is 2.6G at the moment (fresh packed) Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp7sVdJVHtCm.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 11:06:35AM -0500, Paul Winkler wrote: > On Mon, Nov 28, 2005 at 04:29:22PM +0100, Gerhard Schmidt wrote: > > I don't have exakt numbers. We started with pcgi and had heavy problems > > under load. They disapeared with the fastCGI module coming wird zope 2.6 > > i gues. I ve tried mod_proxy back than but had many problems. I can not > > test on the Production system as there are 4 users on the system and > > we have enougth Problems with Readconflictes and Session problems. > > I'm not surprised you had problems with PCGI, it was known to be > extremely slow. AFAIK it ran zope in single-threaded mode so > concurrency was terrible. > > It sounds like you have concluded that, because FCGI is faster than > PCGI, then FCGI must also be faster than mod_rewrite / mod_proxy. > That's just not logical. No, I just described the way we came to fastcgi and that it solved some of the Problems back than. I pretty sure that mod_proxy is much better than pcgi was. But logic tells me that it can't be better than fastcgi. Building a new connection costs time and CPU power and as the this connections have to be build for each request the impact grows with the number of requets. > p.s. If you're having session problems and read conflicts with 2.6, > you should strongly consider upgrading to *at least* 2.7.3 and maybe 2.8. > Heavy use of sessioning is still not perfect (see Dennis Allison's > recent threads), but it is *much* better since 2.7.3. > In addition, ReadConflictErrors are greatly reduced since the > release of ZODB 3.3, which first shipped with Zope 2.8. We are running zope 2.7.8 at the moment and working on mirgating to 2.8.x at the moment exaly for this reasons. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpcTtGXzcgnf.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 04:09:31PM +0100, Andreas Jung wrote:
>
>
> --On 28. November 2005 15:52:25 +0100 Gerhard Schmidt <[EMAIL PROTECTED]>
> wrote:
>
> >
> >Sure I object. Why should perfectly working code be removed. There is
> >no alternativ for heavy loaded sites which need integration of apache
> >and zope. mod_proxy is no alternativ because it raises the load even
> >further.
> >
>
> I've seen lots of heavy loaded Zope sites - I've not seen a single one
> using FastCGI. Can you give us some number about the FastCGI performance
> compared to the standard mod_rewrite approach? Let numbers speak
I don't have exakt numbers. We started with pcgi and had heavy problems
under load. They disapeared with the fastCGI module coming wird zope 2.6
i gues. I ve tried mod_proxy back than but had many problems. I can not
test on the Production system as there are 4 users on the system and
we have enougth Problems with Readconflictes and Session problems.
> But please read carefully...I wrote about deprecating the module but not
> about removing it as in my original posting. We want o make clear that
> FCGI is not supported.
Yes but if its deprecated it can disapear from any new version. And thats
an situation i'm not very comfortable with.
> You are of course free to use it as long as you need.
I know. I will read me in the FCGIServer and see if I can understand how
its work. But my time is Limited. (Running and developing a portal for i
4 user with 3 Fulltime workers isn't that easy).
Bye
Estartu
Gerhard Schmidt| Nick : estartu IRC : Estartu |
Fischbachweg 3 || PGP Public Key
86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request
Germany||
pgp2lPpn79f7a.pgp
Description: PGP signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 03:23:04PM +0100, Andreas Jung wrote: > > > --On 28. November 2005 13:28:20 + Jens Vagelpohl <[EMAIL PROTECTED]> > wrote: > > > > >On 28 Nov 2005, at 13:25, Gerhard Schmidt wrote: > >>>It's a matter of resources, plain and simple. No one has stepped > >>>forward to support it, so it atrophied. If you think it's a great > >>>thing to keep, volunteer. > >> > >>I would if I had the time and the knowlege. But I don't see a Problem > >>with the Code right now. As I said i runs here perfectly smooth. > > > >"It works" and "is supported" are two different things. "Is supported" > >also means there are people who will come forward and help out when the > >code breaks or when people ask questions about it. As you have seen > >yourself, no one does. The answer is (and will remain, unless someone > >volunteers): Use at your own peril. > > I agree. There should be one supported way to achive a goal. In the past we > had at least three methods to run Zope (fortunately we kicked PCGI support > in the past). My suggestion is to deprecate FCGI officially in the docs and > through a deprecation warning and to kick it at some time (not necessarily > after two release cycles). So people can still use but they should know > that they are using a deprecated feature...objections? Sure I object. Why should perfectly working code be removed. There is no alternativ for heavy loaded sites which need integration of apache and zope. mod_proxy is no alternativ because it raises the load even further. Bye Estartu - Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW & Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage pgpwSrYnShhnN.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 01:07:49PM +, Jens Vagelpohl wrote: > > On 28 Nov 2005, at 13:05, Gerhard Schmidt wrote: > > >On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote: > >> > >>On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: > >>>I know there is a way to do just the same with mod_proxy, but > >>>mod_proxy does > >>>open new connection for every request while fastcgi uses the same > >>>connection > >>>for all requests. The is no problem on low load. But with growing > >>>load, this > >>>can become a Problem. > >> > >>Well, it's not "a way to do it", it's *the* way. > > > >Thats a real good argument. There is no *the* way. Every situation > >is different and having as mutch possibilities as possible is > >allways the > >best way to do it. > > It's a matter of resources, plain and simple. No one has stepped > forward to support it, so it atrophied. If you think it's a great > thing to keep, volunteer. I would if I had the time and the knowlege. But I don't see a Problem with the Code right now. As I said i runs here perfectly smooth. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpTIRPlMin9i.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote:
>
> On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote:
> >I know there is a way to do just the same with mod_proxy, but
> >mod_proxy does
> >open new connection for every request while fastcgi uses the same
> >connection
> >for all requests. The is no problem on low load. But with growing
> >load, this
> >can become a Problem.
>
> Well, it's not "a way to do it", it's *the* way.
Thats a real good argument. There is no *the* way. Every situation
is different and having as mutch possibilities as possible is allways the
best way to do it.
> I highly doubt that your assertion about using more connections than
> just one is a problem, under any circumstance. All very large
> production sites that I ever dealt with use mod_rewrite/mod_proxy. It
> simply is not a problem. Or do you have proof?
Im runnig a very large site with 4 users and a peak arround 60 Requests
per second. Having to call connect end all the routines that come with it
is quite an increased load. Why. FastCGI work perfectly and efficiently.
Thats exactly the usecase Fastcgi was developed for.
In none of the Postings is an reason why FastCGI ist bad and therefore not
supported in the future. Just to say "so it is" is not an Answer.
So my question is still there.
Bye
Estartu
Gerhard Schmidt| Nick : estartu IRC : Estartu |
Fischbachweg 3 || PGP Public Key
86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request
Germany||
pgp4uCwucIzhm.pgp
Description: PGP signature
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] why will FastCGI not be supported in the Future.
Hi, I'm a little bit puzzled why there are growing Number of Mails telling that the support for FastCGI will disappear in the future. Why is this. I am running multiple sites that are hybrides of apache/php and zope. It's very easy to set up such a config with mod fastcgi and Apache. It works just fine and very stable, even on heavy load. The posibility to Easy integrate Zope in existing apache/php server was one of our main reasons to use Zope. I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Bye Estartu -------- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp5ZKaBEW8g5.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
